Ouch - I just discovered an easy way to generate kernel panics this morning...
I generally use VMware Fusion for my day to day virtual machines (used for regular office work for Windows only apps, Ubuntu and CentOS for various Linux tasks and testing, etc.)
I'm testing some zfs replication tricks with Solaris and OpenSolaris in VMs and all is good. Except that I wanted to check out the latest patches that are included in the beta builds of OpenSolaris (download from
genunix.org) and for whatever reason, it doesn't like Fusion (or Fusion doesn't like it). Booting from the iso image, it complains about not being able to do a file dump and reboots continuously.
So I figure that I'll use Sun's VirtualBox since it ought to have better general compatibility with the Solaris family (and it's already installed). Which it does and it works perfectly, although I still take exception to the lame approach to managing virtual disks and iso images - whatever.
But then I want go grab some of my scripts from inside one of the Fusion based OpenSolaris VMs so I fire up Fusion. And then I start up the Fusion VM and boom! Kernel Panic.
So the moral of the story is: you can use as many OS X desktop virtualisation products as you like, just not at the same time...
Environment : MacBook Pro, Snow Leopard 10.6, VMware Fusion 2.0.6, Sun VirtualBox 3.0.8
Oh - and if you try to attach a VirtualBox VM network adaptor to a VMware virtual interface, the VM won't start. But since you can't start up a VirtualBox VM at the same time as Fusion VM, putting them on the same virtual network segment is sort of pointless.
infrageeks
Comments