- MAC OS X 10.9 IMAGE FOR VMWARE INSTALL
- MAC OS X 10.9 IMAGE FOR VMWARE 64 BIT
- MAC OS X 10.9 IMAGE FOR VMWARE SERIAL
- MAC OS X 10.9 IMAGE FOR VMWARE FREE
T15:47:40.360Z| vmx| I120: USBGL: Closed arbitrator connection T15:47:40.359Z| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter T15:47:40.354Z| vmx| I120: SVMotion_PowerOff: Not running Storage vMotion. All of this appears _before_ the beach ball. It looks as if the VM itself is deciding to stop some hardware in the middle of executing. Before I see the beach ball appear, these are the last log entries, and no new ones appear once the beach ball appears. Here is the vmware-8.log, and I think the way it ends is a bit weird. SMC::smcGetKeyInfoAction ERROR WKTP kSMCSpuriousData(0x81) fKeyHashTable=0x0xffffff8013054000ĪCPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out SMC::smcInitHelper ERROR: MMIO regMap = NULL - fall back to old SMC mode etc (I have to retype these so I'm skipping a few as this is easily replicated). SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound) SMC::smcReadKeyAction ERROR: $Num kSMSKeyNotFound(0x84) fKeyHashTable=0x0
SMC::smcReadKeyAction ERROR: smcReadData8 failed for key $Num (kSMCKeyNotFound)
MAC OS X 10.9 IMAGE FOR VMWARE SERIAL
Then some serial port initialization stuff When I do that I get a number of errors before it stalls:īootCacheControl: Unable to open /var/db/aylist: 2 No such file or directory I used the force EFI on next boot option and booted OS X in verbose mode from the EFI prompt by executing the following commands from the "unsupported" EFI Shell.įs0:\System\Library\CoreServices\boot.efi -v
MAC OS X 10.9 IMAGE FOR VMWARE INSTALL
You can also follow instructions available by searching the web for creating bootable 10.9 install media from the App. FYI for anyone attempting to replicate, you have to extract BaseSystem.dmg from the InstallESD.dmg (it is a hidden file) and choose that as what you mount as the install media.
MAC OS X 10.9 IMAGE FOR VMWARE 64 BIT
vmx file for the OS X VM on the ESXi host also had the ICH and SMC flags and it did have those flags set (not surprising as the Vsphere client did show OS X 10.7 64 bit as the platform). I get the same behavior, where the progress icon begins to spin for maybe ten seconds or so, then halts, and the mouse icon turns into the beach ball.
I made the configuration change described and rebooted the VM with ESXi 5.5 in it, then attempted to start the OS X VM. I've googled around for it and I mostly find kludgy discussions of trying to run ESXi 5.1 and installing OS X on non-Apple hardware. All of this is being done on a current model Mac Pro. I've tried upgrading it to hardware version 10, I've tried moving an existing Fusion vmdk into place and booting it (which ESXi doesn't like at all). If I then power on the VM with the console open, it starts to boot, showing the gray screen with a slightly darker Apple logo, the progress indicator starts to move, and then after 10-20 more seconds, I get the beach ball icon, which spins endlessly. I set the optical drive to be attached at power on and to use the host device.
MAC OS X 10.9 IMAGE FOR VMWARE FREE
I then create a new virtual machine, declaring it as a 10.7 64-bit system, allocating 4GB of ram and 25GB of disk (which leaves approximately 7GB free on the ESXi host datastore). I attached InstallESD.dmg (and I've also tried creating a custom mavericks iso) as a virtual device on the Fusion-based ESXi host. My current setup is ESXi 5.5 running inside a Fusion 6 VM, with 8GB of RAM allocated and 40GB of disk. I've tried this a couple different ways and I always get the same result, which is a spinning beach ball during the boot process.
0 kommentar(er)
