VMware Fusion for Apple Silicon Public Tech Preview Now Available
blogs.vmware.com
blogs.vmware.com
What about x86 emulation?
We get asked regularly about running x86 VMs on M1 Macs. It makes total sense… If Apple can emulate x86 with Rosetta 2, surely VMware can do something too, right?
Well, the short answer is that there isn’t exactly much business value relative to the engineering effort that is required, at least for the time being. For now, we’re laser focused on making Arm Linux VMs on Apple silicon a delight to use.
So, to be a bit blunt, running x86 operating systems on Apple silicon is not something we are planning to deliver with this project. Installing Windows or Linux from an x86 ISO, for example, will not work.
https://blogs.vmware.com/teamfusion/2021/04/fusion-on-apple-...
ps. currently 2 out of 459 processes on my desktop are running in x86 emulation; sourcetree and some speech synthesis thing.
Granted, I never got to try M1s, but this is plenty faster than my the Macbook Pro "16 for anything, and I hardly ever hear the fan. Battery life is still something that Apple has an upper hand on, but other than that, x86 seems to still be doing well.
I could very well be wrong here, but I don’t think running Desktop Linux in a VM is a very large market, and I would just use Docker to run CLI tools. There aren’t really any Killer X Windows Apps that won’t run natively on macOS?
I suspect they just don't want to publicly commit to Windows compatibility due to licensing issues.
Not really. It is a long way behind Rosetta.
(Partially because Apple only built the M1 to be optimised for running Mac apps in emulation, partially because Apple had spent five years deprecating older software very aggressively so nobody expected those things to work, partially because it's genuinely hard, and partially because it's not very good.)
(Source: I recently left VMware)
What the Insider ARM builds did give you that hasn't been in a release version (until tomorrow) was x86-64 emulation support and a few other minor ARM improvements and an easy way to source a compiled ISO directly from Microsoft.
As far as activating a standard Windows 10 license will activate Windows 10/11 for ARM even if the EULA says it won't and, regardless, switching to Insider builds doesn't sidestep licensing as you need to be licensed to join a PC to the program and the ISO installer has the same licensing and EULA requirements as a normal installer ISO.
Also, VMware is ready to add ARM64 Windows support if Microsoft creates a legitimate way to license it.
99% running Linux, mostly a VM on which I run copies of most of my employer's non-infrastructure software for development and testing.
0.9% running Windows.
0.1% running MacOS. Generally this is only when I've found some bug and want to reproduce it on a clean system to make sure it is not just due to something I misconfigured before reporting it.
Is Debian ARM Linux going to work on an M1 under VMware Fusion? If so, maybe I'd still find VMware Fusion useful on an M1 (we use Debian at work, and I'm fine using Debian for my personal VMs that need Linux).
The value of virtual machines is to be able to virtualise a specific platform! That Win7 machine has software that needs to keep running. There is no Win10 porting or equivalent.
It’s 100% possible to implement this, VMWare is just a second-rate virtualization platform these days.
Don’t buy their product. Ever.
https://www.theregister.com/2016/01/27/vmware_fusion_and_wor...
It’s just a matter of fact they fired/restructured/outsourced, whatever the hell you want to call it, so they could hire cheaper developers to simply maintain the product.
VMWare would almost certainly offer this capability if it wouldn’t require the outsourced team 2x, 3x, …, 10x the amount of time it would would have taken the team who originally built the software.
Fusion and Workstation inherit most of their underlying capabilities from ESXi. Barring a few functionality/usability flourishes unique to workstation/desktop use cases...if ESXi doesn't do it, Fusion and Workstation won't.
As for VMware's platform being second rate - there's still not really a lot of serious competition in the on-prem world, especially if any kind of scale, extreme performance needs or operational complexity is required. Nitro certainly runs circles around it in some regards, but that's not really an option that's on the table for big on-prem shops.
I have to question, then, what is Fusion meant to do? I have primarily used it to install x86 OSes.
Parallel’s icon literally has a Windows logo in it.
Sort of like Ford gets asked regularly about driving their cars on interstate highways ?
This is not a fringe feature or some weird corner-case ... this is the reason people buy your product.
Desktop is a niche for VMware, and Mac a niche within that. It seems pretty straightforward that perhaps this product doesn’t pay for a whole new engineering skill set.
Virtualization isn't emulation. Expecting seamless execution of x86 Win code on an M1 Mac seems unreasonable to me. I was initially concerned about this, but I realized that I've almost completely stopped using local VMs at all in favor of VMs in our datacenter, and so ...
That's where VMware started: The original VMware product started the whole x86 VM field before Intel provided any virtualization capabilities. VMware's first product, able to run Windows VMs smoothly in a window, was amazing compared to what had come before, and they did it before there were any x86 features for virtualization, using clever code scanning and emulation techniques. It's not at all obvious that they couldn't use similar clever techniques again, combined with Rosetta 2 style JIT - if they wanted to.
As you note, emulation products existed prior to the Intel switch, and they would do in a pinch, but they were VERY slow because emulation != virtualization. Doing anything complex in an emulated environment was PAINFUL.
Running Windows in a Parallels or VMWare virtual machine on my Intel Mac works VERY well, but no emulation product will deliver that level of performance.
You could of course virtualize ARM Windows on an M1, I suppose, but then you're not in an Intel environment, and the ARM Windows software landscape is thin.
It works totally fine
I hope vmware fusion works as well because Parallels has become annoying over the years. You can buy a permanent license instead of a subscription, but you have to upgrade every time MacOS has a major update anyway.
No x86 VMs from either virtualization product means I also need a x86 box around. What does that lead to? I'm no longer a Mac Pro customer, just a Mac Mini customer. And I'll be running Linux as the main OS on the x86 box, which I haven't done in ages.
Are they trying to push Linux/x86 adoption? :)
Edit: at least they were honest enough to announce the transition early. I would have bought a new Mac Pro last year otherwise.
Yeah, but they're reasonably influential. At least my friends ask me what to buy. Not that I always recommend Apple, but they know I use that exclusively which counts for some mind share. And that will end when I make the jump to arm.
So now I just don't buy the professional version any more. And I'm saying both companies are shady as f*k.
With VMware Fusion, OpenGL worked out of the box and Extreme Tux Racer and ShaderToy ran fine.
Also, in VMware Fusion I could disable all MacOS-shortcuts (like Spotlight and switching spaces) while the VM is in full screen... With Parallels I would always switch spaces by accident because I couldn't find a way to disable everything...
Parallels brings their own drivers to install, which means not every Linux version is supported, the last time I tried it was lacking drivers for the newer kernels, this seems to have improved somewhat.
VMWare requires a few more clicks to configure with the upside that you have a clear configuration process so little magic is happening in the background - Parallels seems to automatically mount your drives in the VM which often is not what I want it to do.
Also, VMWare supports platforms beyond the Mac, so if you have a mixed environment, you can even move VMs between e.g. Windows and Mac machines.
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?
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.
Their slow implementation of virtualization is just another piece to the puzzle. Realize that while Parallels was super quick to deliver, even docker was faster than the “worlds leader in virtualization “.
Parallels also appears to have had early access to M1 that VMware did not.
So for my cute metaphor, which I look forward to improvements, I think of the general problem as "we need to run a business" as an analogue of "we need to run an operating system and some programs"; the machine architecture is the amalgamation of tools and techniques.
So if a business springs up as the form of a restaurant, and that business as operating system learns how to create successful patterns using spatulas and fryolators and hot plates, then to move your business to a farm that has tractors and shovels and troughs, you basically have to start all over with your implementation even if your business plan is the same.
But, as those patterns become satisfied, of "get my pile of stuff moved from this container to that container", the issue of plates and troughs becomes solved and you get rapid springs forward of completing your task of migrating.
I have no credentials to answer this basically but that's how I imagine it.