A new feature that appeared in VMware Fusion 7 Pro was its new ESXi management. This included the ability to upload VMs from Fusion directly to an ESXi server. However, when I tried to upload OS X VMs something seemed to go wrong. The upload would work, but the OS X VM would then hang on boot.
Non-OS X VMs were uploading fine, so the problem was specific to OS X VMs. Since I could still build OS X VMs using the Windows vSphere client, I didn’t invest a lot of time into solving this issue. Fortunately, Calum Hunter was more motivated in this regard and found a solution.
There are a few things to know about if you want to upload an OS X VM to an ESXi server running 5.5, so I’ve put together a procedure for those who want to leverage Fusion 7 Pro to upload OS X VMs. See below the jump for the details.
VMware has released the VMware Fusion Technology Preview July 2014 as of Jul 3, 2014. One of the new items included in the Features list was this one:
Support for viewing VMware Fusion Professional to VMware Workstation, VMware ESXi, VMware vSphere servers in the library (File > Connect to Server)
When I investigated, it looks like this feature brings to VMware Fusion something that’s been in VMware Workstation for a while: a way to manage free ESXi and paid vSphere servers.
For more details, see below the jump.
In Mac OS X Server 10.7.x and 10.8.x, there’s been an issue that Mac admins have run into more than once:
Profile Manager in 10.7.x and 10.8.x also has an known issue where it crashes when set up in a VM. The root cause is the same: Profile Manager needs to have Open Directory running and Open Directory won’t turn on.
The fix for this issue in 10.7.x Server and 10.8.x Server is simple – give your VM more than one processor. Once you give the VM multiple processors (two is fine), Open Directory should begin working. This will also fix the Profile Manager crashing issue, as Open Directory should now enable properly.
In Mavericks, it appears Apple has addressed this issue. In my testing, Open Directory no longer requires multiple processors.
Now that Open Directory can run with one processor, Profile Manager also now runs properly on a one-processor VM.
For those who wanted a copy of my virtualization talk at MacTech Conference 2013, here are links to the slides in PDF and Keynote format.
Keynote – http://tinyurl.com/mt2013vmkeynote
I’ve updated the create_vmware_osx_install_dmg.sh script that I had previously posted about here. The script now includes support for Mavericks, so the script can now be run on 10.7 – 10.9 to create custom OS X 10.7.x, 10.8.x and 10.9.x installers for VMware Fusion and VMware ESXi. See below the jump for the details.
This ability has been hugely useful to me and I’ve long wanted that same flexibility when building ESXi-hosted VMs. With the release of ESXi 5.5, VMware has now included NetBoot support for OS X VMs on ESXi. This gives me the ability to build VMs on an ESXi host using the same DeployStudio-driven deployment process that I’ve been using to build VMs in Fusion.
Needless to say, this greatly simplifies my build process and all but eliminates any need for me to build OS X VMs in Fusion first and then transfer them to an ESXi server. Thanks to the folks at VMware who built this support into ESXi; it’s going to make life a lot easier for Mac admins who want to virtualize OS X.
In the wake of VMware’s release of ESXi 5.5 on Monday, September 23, I needed to upgrade my home’s ESXi 5.1 server to ESXi 5.5. Since I didn’t want to fire up my Windows VM, I did the upgrade from 5.1 to 5.5 via SSH and esxcli. For those interested, see below the jump for the details of the process I used.