If I open VM ware Fusion 12.2.4 ther is an error code.
Transportfehler (VMDB) -14: Pipe connection has been broken
Does anybody know what to do?
MAC OS 12.6
It looks like Apple is secretly preparing a 32” iMac, which could fit your needs: but probably not before next year.
BTW, a question to the experts (I, too, am slowly looking for an Apple Silicon MacBook Air or Pro): is there any advantage, for virtualization, to get 24 (Air) or 32 (Pro) GB of RAM…? Here, I’m thinking more about Windows 12 as a guest, which will probably require 8 GB RAM: which could become 16 GB if nested virtualization will finally become a reality and WSL/WSA is run inside the VM, thus leaving 8 or 16 GB to the host. So RAM is probably best maximized. And what about the M2 Max? Better for virtualization, or similar in VM performance to the M2 Pro?
My rule of thumb has always been to get as much RAM as you can afford.
According to the Asahi Linux folk, the M2 series does support nested virtualization. But, Apple's Hypervisor.framework doesn't provide access to that as far as I know.
I presume you mean windows 11. For that 8 is fine.
Don't count on nested virtualization being available. Apple has to change their internal APIs, and there's not much use case for it (but you never know). Plus, I'd expect it would only virtualize ARM code not the x86 emulation layer.
If you can afford the Max, definitely go that route. Lots more graphics cores (mine runs 3 5K monitors plus the internal without skipping a beat).
Note that the old guidance about leaving cores for the host and total allocation doesn't really carry over from intel to arm. During my TP upgrade last week I had 6 VM's running at once, 8-16 GB each, minimum of 4 cores each, and the machine never even turned on the fans. That's on a 64GB max.
"Plus, I'd expect it would only virtualize ARM code..." that is what rumors are telling and which might be a possible solution. On one hand Apple skipped Bootcamp and told virtualization is the new way, on the other hand they have not done much for it till now. But an 32" would be really nice...
Don;t rule out the Mac mini with a large monitor. If you're serious about minimizing e-waste, a mini with an ultra wide monitor means down the road you just replace the CPU and not have to get a new monitor. And the mini doesn't take up that much desk space.
100% agree - and it's FAR more repairable. The iMac is fine for certain niche use cases, but overall, the Mini is a far better answer (especially given Apple's vastly overpriced screens).
Yes the mini is alive and well. It’s available with M2 and M2 Pro configurations. The Apple Silicon versions really resurrected it compared to its Intel predecessors.
I own several Mac Minis spanning examples of each major generation of the design and processor architecture. Some of the later Intel ones (especially the 2012 and 2018, the latter had a minor tweak in 2020) had fairly good high end configurations for CPU cores and memory as long as you weren't worried about GPU performance. I also have an M1 Mac mini for testing (deliberately bought with minimal specs). I haven't bought any of the M2 models yet but am keeping a close eye on the options should the need arise.
The current M2 and M2 Pro models are good candidates for running ARM VMs, and the Apple Silicon GPUs are a lot better than Intel's ones. Basically go for the M2 Pro if you want more CPU, GPU, memory, Thunderbolt ports, displays, or need more than 2 TB internal storage and are willing to pay Apple's excessive storage upgrade prices.
Note that if you are considering a Mac Mini with M2 Pro and intend to upgrade any of the components from base level, you should do a comparison with the Mac Studio with M2 Max: the price is basically identical if you get the Mac Mini with M2 Pro and upgrade CPU/GPU, 32 GB memory and 10 Gbit Ethernet, compared to the base Mac Studio with M2 Max - the latter has yet more GPU cores and supported displays, and adds the front ports, at the cost of a taller body with a bigger cooling system (reports are that the fans in the M2 generation of Mac Studio are usually silent, unlike the previous M1 generation).
The Mac Studio can step up even further to the M2 Ultra, which doubles the starting price for twice as much of everything internal (and the two front USB-C ports become Thunderbolt).
Thanks… There’s also the option to get an M1 Max 16” 32 GB MBP with one of the recurrent deals on Amazon and others (1 k€ discount, compared to a similar M2): if nested VMs won’t be supported by Apple anyway in the foreseeable future, M1 or M2 makes little difference. (BTW, I talked about Windows 12 because there is a rumor that it will require at least 8 GB of RAM: so, having only 16 GB on the host might be a bit limiting, in the future.)
Maybe there will be nested virtualization in macOS 15 (Mammoth? a big update?), who knows. Anyway, Apple should show more interest for virtualization: the progress has been rather slow, so far…
@mdbergmann2 That file doesn't contain enough information to help figure out what's wrong. Could you please attach the vmware.log and mksSandbox.log files that are found within the VM's bundle?
They can be found by:
Zip them up and attach them to a reply.
Also, it appears that you are trying to power on a VM that's on a volume called "Extended". How is that volume formatted (APFS, HFS+, MS-DOS/FAT, or ExFAT)?
I'm seeing out of the log that you're running a Mac with an i7-4790HQ processor. That's either a MacBook Pro 15" late-2014 or mid-2015. The mid 2015 model is supported by Monterey, the late 2014 is not. Which MacBook do you have?
I'm asking because the symptoms are consistent with Macs that are running OpenCore Legacy Patcher to run macOS on unsupported hardware. The logs abruptly stop as soon as the VM is powered up, which we've seen in OCLP enabled Macs as the Apple Hypervisor crashes/doesn't start properly.
Just want to make sure that is or isn't the case in your situation.
It's a mid-2015 MacBook Pro.
Though I must admit I had a CoreLegacy Venturer System running for a short while, but it caused problems so I completely reinstalled supported Monterey on this laptop.