For a couple weeks now, I’ve been using Xcode 4.3.3 and the iOS 5.1 SDK on a mid 2012 MacBook Air 13″ with 8GB Ram. It’s very nice.
With the July 16th update to the iOS 6 development betas, it was time test running the new Xcode environment under a VM on the MacBook Air. The first step in the process was to get a virtual instance of OS X Lion 10.7 running under VMware Fusion.
I’ve done this before, but the new 2012 MacBook CPU (Intel Ivy Bridge) caused a “CPU disabled by guest operating system… ” error under Fusion. The solution was to add this line to the *.vmx config file of the target VM.
cpuid.1.eax = “—-:—-:—-:0010:—-:—-:1010:0111”
VMware should have a 2012 update to Fusion for OS X Mountain Lion 10.8, they are currently testing it as a “technical preview”. This post provides more information on the error and it’s solution.
With that problem solved, it was time to get Xcode 4.5 beta 3 up and running. Right after installing VMware Tools and configuration some OS X settings to my preferences (I didn’t use Migration Assistant for this VM as I wanted a fresh environment).
The next issue was with the Xcode 4.5 app. It would not run. I used Lion 10.7.3 to create the VM the new beta requires a minimum of 10.7.4. Using software updates to get 10.7.4, iTunes, and Safari updates downloaded about 1GB. After the updates, the Xcode 4.5 beta is now able to run. This is a good place to make a backup of the VMDK and save for future use.
VMware snapshots or Fusion Time Machine integration are both good features, but I prefer to locate the *.vmwarevm file (package) in Finder and copy to a compressed zip file. I’ll use this zip as a clean start for additional beta releases as well as some OSX Server testing. Will also use it to testing the Mountain Lion upgrade.
After installing Xcode, you’ll most likely want the ability to do something with it. This entails installing some “core libraries”. From within Xcode Preferences, the Downloads tab provides access to additional Components and Documentation. Plan for another GB or more of downloads.
If you’re setting up your virtual dev/test environment for first time, plan on 4 or 5 hours and several GB of downloads/updates during the process. After that you’ll be able to test beta releases or do other experimental work in a VM (with USB access to physical devices if desired) without affecting any of the apps of your host Mac.