Mac unable to find driver for this platform acpi mac os x#
Mac unable to find driver for this platform acpi mac#
Mac unable to find driver for this platform acpi windows#

Mac unable to find driver for this platform acpi mac#

Thankfully, VMs don't need to strictly correspond with physical Mac configurations that Apple has manufactured, but the greater the difference, the more likelihood of running into some odd problem as a result.

You're well into uncharted territory: Your VM is a two-socket, 4 core-per-socket system with only 32-bit processors, which can't possibly correspond to any physical Mac. The purpose of these 32-bit VMs is to simulate a 32-bit Intel Mac with a Core Solo or Core Duo processor, like iMac4,1, iMac4,2, MacBook1,1, MacBookPro1,1, MacBookPro1,2, Macmini1,1

Mac unable to find driver for this platform acpi mac os x#

The Mac OS X bootloader always has the final say, and it doesn't always do as we wish. Unfortunately, there is no way for us to absolutely force Mac OS X to use either the 32-bit or 64-bit kernel. After I shut down the VM, vSphere changes it back to 'Apple Mac OS X 10.6 (64-bit)' again. I have another working VM set to 'Apple Mac OS X 10.6 (64-bit)', but after it finishes booting, this automatically changes to 'Apple Mac OS X 10.6 (32-bit)' in vSphere, and 'uname -a' in that VM shows 'RELEASE_I386' not 'RELEASE_X86_64'. It appears that VMware doesn't honor this setting. Has anybody run into this before, or into any similar problems running a 32-bit guest OS on a 64-bit host? Any idea what I should try to fix it or more importantly prevent it from happening again? I have compared the vmx file of a 64-bit Snow Leopard Server VM with one of the kernel panicking 32-bit Snow Leopard Server VMs, and I don't see any relevant differences. I did not see anything in the VMware knowledge base article about hardware versions that would suggest upgrading the hardware version would help with this problem.

All my VMs are using hardware version 8, which is the last version compatible with ESXi 5.0.0, just in case I have to downgrade to ESXi 5.0.0 for some reason. I realize the last supported version of ESXi for the Xserve is 5.0.0, but 5.0.0 has some bugs, including a dialog box in vSphere Client that must be dismissed any time a VM using a recent version of macOS that is configured with more than one core is started or restarted (which states erroneously that the VM may be unstable with more than one core), so I would rather use a newer version. I realize ESXi 6 includes the Embedded Host Client at but I usually avoid it because it seems to be missing some functions. I know this setup has some quirks but I'm accustomed to them.

Mac unable to find driver for this platform acpi windows#

I have been managing ESXi using the Windows VMware vSphere Client version 6.0.0U2 running in wine on OS X El Capitan. The other 32-bit VM was just set up a couple days ago, and was working until I edited the VM settings to increase the amount of RAM, and now no matter what I do, including changing the amount of RAM back, it kernel panics at boot.

One 32-bit VM was working fine for a week or two, until I edited the VM settings to increase the amount of VRAM, and now no matter what I do, including changing the amount of VRAM back, it kernel panics at boot. Panic(cpu 0 caller 0x563ebd): 'Unable to find driver for this platform: 32-bit VMs are configured with OS 'Apple Mac OS X 10.6 32-bit' and the 'monitor_control.disable_longmode' vmx option set to 'true'. They both initially worked but are now experiencing the same kernel panic immediately after startup. I've tried two different VMs on two different Xserves. But I'm having trouble with Snow Leopard Server in a 32-bit VM. I've set up virtual machines running various 64-bit versions of macOS from Snow Leopard Server (10.6) to El Capitan (10.11) and they work fine. Hello, I have a number of 64-bit Apple Xserve3,1 servers running ESXi 6.0.0U2.