OVA file made with VirtualBox 4.0 can't be read by VMware ovftool

Description

I created a 32-bit openSUSE 11.3 virtual machine using VirtualBox 4.0.0 on a 64-bit openSUSE 11.3 host. The machine works fine. I then exported it to an OVA file using the Export wizard, which did not report any errors. But when I try to read it into VMware using VMware's "ovftool" conversion utility, "ovftool" reports an error:

I've attached the XML 'ovf' file - it is indeed calling this a 'virtualbox-2.2' machine, which the VMware tools apparently do not support. I haven't checked the VMware documents yet to see what they do support, but I can do that if you don't have that filed away somewhere.

I tried to change this VirtualSystemType. I am not yet familiar with ovftool, but using vSphere client with ESXi 4.1. Just for the record, with File -> Deploy OVF Template... I got:
"File <...>.ovf fails integrity check and might have been corrupted during transfer.". Fortunately I selected the disk format to vmdk when I installed the VM. So I created a VM in ESXi without a virtual HDD, uploaded the vmdk (the one in the VM, not the exported one (that did not work)), added a new virtual HDD from existing file (from the vmdk just uploaded) and the VM worked.

This issue exists because the v2 OVA/OVF that Virtualbox produces isn't recognized by VM's ovftool yet (they do 1.0 and 1.1), the DTMF does recognize v2 as a valid release though. As indicated above, the correct way to work around this is to 'vboxmanage export VM_NAME' or use the UI and select v1 when exporting, then use the ovftool to convert to VMX or a VMware compatible OVA by using 'ovftool --lax orig.ova dest.ova'.