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.
As part of my FileVault 2 testing, I do a lot of work with OS X VMs running in VMware Fusion. With 10.8.5′s release yesterday, I built a new OS X VM using this process. Once it was built, I tried enabling FileVault 2 and hit an odd issue. FileVault 2 was reporting that it was enabling, but on reboot I was not getting the FileVault 2 pre-boot login screen. Instead, I was passed onto the regular login window.
This is not the correct behavior for FileVault 2, so I was concerned that something in Fusion 6 had broken my ability to work with FileVault 2. After some work though, I was able to get FileVault 2 working again in VMware Fusion 6.0. See below the jump for details.
An issue that I’ve been dealing with for a while has been that Oracle’s Java 7 did not run natively in VMware Fusion. VMware had created a patch for OS X VMs, but it was only designed to be run in OS X VMs running 10.8.x.
As of today, that issue has now been resolved. With the release of Java 7 Update 40, Java 7 now runs natively in VMware Fusion OS X VMs running 10.7.5 and 10.8.4. Thanks to the OpenJDK team, Oracle and VMware for their work in getting this fixed.
I’ve updated the create_vmware_osx_install_dmg.sh script that I had previously posted about here. It now includes the ability to create an .iso file, which can be used with VMware ESXi servers running on Apple hardware. See below the jump for the details.
My preferred way to create VMs in VMware Fusion is by leveraging NetBoot and DeployStudio, but not all environments have access to NetBoot or DeployStudio. For those environments, there’s now a scripted way to create customized OS X 10.7.x or 10.8.x installer disk images for use with VMware Fusion. This allows the creation of OS X VMs in VMware Fusion that can configure themselves in an automated fashion without needing access to either NetBoot or server resources. See below the jump for the details.
Since the process I developed is ultimately about getting the OS X VM’s vmdk file up to the ESXi server, then building a new VM on the ESXi server to use that vmdk file, this is an easier technique because it allows us to skip using VMware Standalone Converter altogether. Instead, this procedure will use the vmware-vdiskmanager tool included with VMware Fusion and the VMware vSphere Client application. See below the jump for details.