Last night I got around to migrating my virtual machines from Parallels Desktop 13 to VMware Fusion 10. It was something that I was dreading because of the time involved to do this. Plus I was expecting to have some problems along the way. But I knew that I had to get it done as I use these virtual machines frequently in my job. Now before I get to the part where I tell you how I did it, let me tell you why I made the move to VMware Fusion 10. There’s three reasons:
- VMware Fusion 10 provides mitigations from the Spectre CPU vulnerability. That’s important to me as I take security seriously. Parallels Desktop 13 doesn’t appear to provide that mitigation which was a concern to me and was the main driver for me to make the switch.
- The secondary reason for me to make the switch was the fact that Parallels Desktop 13 displays ads when you start the program. That’s a total #EpicFail in my mind because if you pay for a product, you should not ever expect to see ads. EVER.
- I did note that in the process of reviewing VMware Fusion 10, it came out as simply the better product as it supports features such as NVMe devices, UEFI Secure Boot, UEFI boot, and TPM chips which means that I can accurately replicate customer environments so that I can understand why they are having an issue, and come up with a fix for it.
So with that out of the way. Migrating from Parallels Desktop 13 to VMware Fusion 10 was mostly easy. The process to migrate is detailed in this VMware document. It’s pretty straightforward for the most part. The only problems that I came across were:
- My Windows 10 and 7 virtual machines had no sound after they came up in VMware Fusion 10. To try and fix that, I tried this VMware knowledgebase document with no success. But thanks to my friend Google I found this discussion page from VMware which worked. Oddly, even though what each documents wanted me to do was largely the same, a couple of things that the VMware discussion page contradicted what the VMware knowledgebase document said. But still worked. VMware needs fix that to make life easier for their customers.
- My Windows 7 VM would not scale the video to match my MacBook Pro’s retina display until I reinstalled VMware Tools. Then it worked fine. I am guessing that something went sideways during the transition which required me to reinstall VMware Tools.
- My Windows XP virtual machine blue screened when it came up after I pulled it into VMware Fusion. Nothing that I did would fix that. Thus I decided to do without it as I haven’t used it in ages.
After that was all done, I deleted Parallels Desktop to reclaim some disk space and the migration was complete. Thus far, I am happy with the results. I should have made this switch long ago as VMware Fusion 10 will make a significant difference for me when it comes to my usage of virtual machines.
#Fail: VMware Fusion For M1 Macs Beta Announced With No Windows Support
Posted in Commentary with tags VMWare Fusion on September 10, 2021 by itnerdI’m a big fan of VMware Fusion as that’s my go to for running virtual machines on my Mac. As you can see, my review of it was very positive. But as I prepare to migrate from my Intel based MacBook Pro to a presumably M1X based MacBook Pro when those appear later this year, it appears that I will likely not be running VMware Fusion. VMware announced yesterday that VMWare Fusion will be coming to M1 Macs with the first beta release compatible with Apple Silicon. But it’s a closed beta that you need to apply for via an online form. A public beta release will be available in about two weeks, which could mean that the official release might come by the end of this year. This news was announced by Michael Roy who manages the VMware Fusion and Workstation product lines via Twitter:
But there is one significant catch. VMware Fusion will not provide support for running Windows virtual machines on Apple Silicon Macs. This is because Microsoft does not sell official licenses to allow you to run Windows 10 ARM on Mac. And to make matters worse, VMware isn’t making drivers and VMware tools software available to allow users to “roll their own” Windows VMs. This was confirmed via another Tweet:
Here’s the problem with this. Parallels has M1 support and allows you to run Windows, and Parallels uses the beta ARM version of Windows to do this. While going this route may bring some legal issues, it is supported. And clearly Parallels isn’t afraid of Microsoft smacking them silly the way that VMware appears to be:
If VMware decides not to bring support for Windows to Fusion and work out something with Microsoft, you can expect a massive defection to Parallels who either have worked out a deal with Microsoft, or simply don’t care. And I will be among them as I need the ability to run Windows 10 and occasionally Windows 7 virtual machines to troubleshoot customer issues and test things like malware in ways that are risk free.
Now maybe VMware has some grand plan to bring Windows support to a future beta. They haven’t said that. But I hope so. Because even though VMware is the gold standard for virtual machines, they don’t currently have a solution for myself and others. And it will end up costing VMware.
Your move VMware.
Leave a comment »