Opened 14 years ago
Closed 14 years ago
#5512 closed enhancement (fixed)
VirtualBox-specific settings should be supported in OVF export too, using the ProductSection element
| Reported by: | Daniel Kulesz | Owned by: | |
|---|---|---|---|
| Component: | OVF | Version: | VirtualBox 3.0.12 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
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.
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
All VirtualBox-specific settings are now preserved in custom OVF tags, starting with version 3.2.
Note:
See TracTickets
for help on using tickets.
This is not just a "nice to have", it's necessary to make some VMs usable. See bug #5062