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.
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.
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.
I’ve started using ESXi servers more and more for hosting my test Macs, both here and at work. As part of that, I’ve found it to be considerably easier for me to build the VM inside of VMware Fusion on my Mac and move it to ESXi, then build it from scratch on my ESXi server.
That said, I’ve found the process for moving OS X VMs has not been straightforward. When I first tried moving 10.8.x VMs, I tried both VMware’s OVF Tool and VMware’s Standalone Converter, but neither initially appeared to provide me with the ability to transfer working OS X 10.8.x VMs.
In the end, I was able to find a way to use VMware’s Standalone Converter to transfer 10.8.x VMs, but the process involves some extra steps on the ESXi server’s end.
The process I’ve developed involves using a Windows 7 VM running inside of VMware Fusion, with the VMware Standalone Converter application installed. One thing to note before proceeding further is that I did not try this with a vSphere server. All my work has been done with VMware’s free ESXi server, so it may be that there’s an easier way to do this with vSphere. See below the jump for details.
One thing I’ve wanted to do for a while is virtualizing my home server setup, as well as making it easier to stand up (and take down) test servers as needed.
I’ve been doing a lot of work with VMWare Fusion on my Mac and could have gone that way, but I wanted to do the virtualization with VMWare’s free ESXi software. I hadn’t previously set up a dedicated hypervisor, so I wanted to learn how to do that.
I have a 2011 Mac Mini Server, which is fortunate because setting up ESXi on that Mini model has been well-documented in a number of places. The latest available version as of this date is ESXi 5.1, so I decided to install that. After some work, I now have ESX 5.1 running on my Mini Server. See below the jump for the details.