I'm not sure if this is a bug or I'm missing something, but if I create a VMX using the "Other 2.6.x Linux (64-bit)" guest type (so that guestOS is "other26xlinux-64"), and then convert it to OVF via ovftool (I tried 1.0 and 2.1.0, both on Linux), the resulting XML seems wrong:
<OperatingSystemSection ovf:id="1" vmw:osType="*other26xLinux64Guest">
Note the id of 1, and the asterisk before the osType string. When importing the resuting OVF (ESXi & vSphere 4.1.0), the guest ends up as "Other (32-bit)", which is incorrect, but more significantly can't even boot until I change it manually to a 64-bit type.
I was expecting the OVF to contain:
<OperatingSystemSection ovf:id="100" vmw:osType="other26xLinux64Guest">
Hand-editing the OVF to fix up the XML works fine, and I could do some sed magic to automate all this, but I'm wondering if there is a reason for this, or a more proper fix?
Thanks a lot for any help
