3 ms·
It's worth noting that the reason this took so long is that VMWare ported their in-house hypervisor instead of using Apple's Hypervisor.framework (or it's highe
by easton 5y ago
It's worth noting that the reason this took so long is that VMWare ported their in-house hypervisor instead of using Apple's Hypervisor.framework (or it's higher level counterpart Virtualization.framework).
I wonder if that means we'll ever get a ESXi port to Apple Silicon. I doubt it, but what other reason is there to go through all this trouble?
- sithadmin 5y agoInternal rumor also had it that VMware got blindsided by Apple's M1 announcement (as opposed to Parallels, who got invited to do a demo at launch). As a former employee (that admittedly only had indirect visibility into such things), relations between the two firms are generally not friendly.
- wila 5y agoThe Hypervisor.Framework was already being used for VMware Fusion 12. It is the main reason behind a lot of the current complaints, like poor performance and network connection issues under certain conditions. There's more than one reason for this VMware to take more time. One of them being that VMware Fusion is part of a bigger picture, like that Fusion needs to work with VMware vSphere from day one. FWIW, there's already ESXi on Arm. I don't know how much more work it is to get that to work on Apple Silicon assuming you are talking about "run it on the metal and not as a VM". Pretty sure they will investigate that route to see how much extra work it is.