Running ETAP on a macOS Virtual Machine: VMWare vs Parallels

When considering the use of ETAP on a Windows virtual machine running on a macOS operating system, two popular virtualization platforms, VMWare and Parallels, have their unique advantages and limitations.

Background

ETAP is a powerful software tool that specializes in electrical power systems. However, running such specialized software on a macOS virtual machine requires careful consideration due to the specific requirements of the operating environment and the hardware components involved.

VMWare Performance

VMWare is known for its robust support and compatibility with a wide range of operating systems. When it comes to running ETAP on a Windows virtual machine on macOS using VMWare, the platform excels in stability and accuracy.

Until recent improvements by Core OS Platform Team at Apple, VMWare had a more reliable method of installing virtualization hooks into the system. This ensured that virtualization was efficient across all CPU cores. Therefore, users experienced a more stable and less crash-prone system. VMWare also correctly virtualizes CPU cycle counters and other clocks, making it a more accurate and performant solution for running Windows applications on macOS.

Parallels Challenges

Parallels, on the other hand, has faced some challenges due to statistical installation methods. In older versions, Parallels would sometimes fail to install virtualization hooks on some CPU cores, leading to instability and crashes. This was particularly noticeable when running multiple CPU-intensive tasks.

Additionally, Parallels has been less accurate in virtualizing certain counters and clocks, leading to issues like kernel panics due to malfunctions in the system's timing mechanisms. Specifically, there were issues with the Mach semaphores and mutex codes, which would intentionally crash if a semaphore was held for too long. These issues became more prominent due to the lack of proper virtualization, causing both temporary and persistent system failures.

Current Considerations

While the server version of macOS no longer enforces clock accuracy, modern systems can still encounter deadlocks from bugs in rarely used code paths. This implies that while Parallels may not cause immediate kernel panics, a deadlocked system can be just as problematic as a system crash, leading to significant downtime and staff frustration.

Hardware and Software Requirements

For those looking to run ETAP on a macOS virtual machine, it’s important to note that the modern version of Windows, Windows for ARM, is not compatible with ETAP’s specifications. Therefore, you will need an older Intel-based Mac, and a Windows for Intel version will be required.

Moreover, to ensure optimal performance, you may need to configure USB passthrough to allow for secure key operations. This setup adds an additional layer of complexity and requires a trained IT staff to manage.

Professional Recommendation

Based on the current state of virtualization environments and ETAP’s specific requirements, my professional opinion is that running ETAP on a Mac is not advisable, especially if the system specs are limited in compatibility and performance. It is generally better to run ETAP directly on a Windows machine or on a Linux host with a Windows dual-boot setup.

If you are set on using a virtual machine, VMWare is the preferred choice due to its more reliable performance and lower risk of system instability. However, if you must use a virtual machine, Parallels would still require careful configuration and may not be the best long-term solution due to its historical issues with stability and performance.