More fun with ovftool

Sun, 20 Sep 2009 14:28:11 +0000

I tried restoring my .ova into vCenter and it failed. It said something like “Device ‘virtual disk’ uses a controller that is not supported. this is a general limitation of the virtual hardware version.” This kind of pissed me off, especially when I couldn’t really find anything in Google about what the error meant, but it turned out to be pretty easy to fix - I just clicked “upgrade virtual hardware” in VMWare Server to upgrade the hardware version from 4 to 7. I then created another .ova, uploaded it to the datacenter and successfully deployed it in vCenter in its own resource pool. Yay!

Exporting VMWare Server VMs to OVA/OVF with ovftool

Fri, 11 Sep 2009 18:56:25 +0000

Well, I thought this was going to be a huge pain in the ass, but it turns out not to be a really big deal. I found this post which includes instructions and a link to download VMWare’s “ovftool”. There’s a win32 version and a 32-bit and 64-bit linux version:

-rwxr--r-- 1 evan evan 19326184 Sep 11 17:16 VMware-ovftool-installer-1.0.0-166674-lin.i386.sh*
-rwxr--r-- 1 evan evan 17212108 Sep 11 17:16 VMware-ovftool-installer-1.0.0-166674-lin.x86_64.sh*
-rwxr-xr-x 1 evan evan 43833393 Sep 11 17:33 jdk-1_5_0_13-linux-amd64.bin*

I installed JDK 1.5.0_r13 because that’s what I had laying around. The 64-bit installer for ovftool ran without a hitch. I haven’t yet tried importing the .ova to my vCenter cluster (the export was from our Vmware Server (free) environment) but the conversion itself seemed fine. The one problem I encountered was that it was complaining that the cdrom was connected. The VM in question had an ISO configured as its cdrom drive, but it wasn’t connected, yet the ovftool still complained about it. I shutdown the VM, deleted the device completely, and then the conversion went fine.

Ovftool on Evan Hoffman

More fun with ovftool

Exporting VMWare Server VMs to OVA/OVF with ovftool