VirtualBox-specific settings should be supported in OVF export too, using the ProductSection element

[DanielKulesz]

It's possible to definesome "ExtraDataItem" fields in virtualbox, such as the following:

<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" value="22"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" value="2222"/>

Unfortunately, these extra data items don't get exported into the OVF format. Therefore importing a previously exported VirtualBox VM in OVF format gets very annoying over time.

The OVF specification Version 1.0 supports such attributes with the <ProductSection> element, as outlined in section 9.5 of the specification. It would be really cool, if VirtualBox would take advantage of this feature.

[auspex@…]

This is not just a "nice to have", it's necessary to make some VMs usable. See bug #5062

[umoeller]

All VirtualBox-specific settings are now preserved in custom OVF tags, starting with version 3.2.