Opened 7 years ago
Last modified 7 years ago
#17691 new defect
Status Window for .OVA Appliance Import as .VDI shows .VMDK File Extension
| Reported by: | slikzzz | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.8 |
| Keywords: | .ova .vdi .vmdk | Cc: | |
| Guest type: | other | Host type: | other |
Description
When importing a .OVA appliance as a .VDI (.VDI file extension manually specified instead of .VMDK file extension in the Virtual Disk Image column), the file name in the status window shows as .VMDK instead of .VDI. The appliance correctly imports as a .VDI file so the bug is just the status window for the import. The attached screenshot shows the .VMDK file name despite the fact that a .VDI file was correctly generated as specified.
Attachments (1)
Change History (5)
by , 7 years ago
| Attachment: | bug_vmdk-vdi.png added |
|---|
comment:1 by , 7 years ago
When importing a .OVA appliance and specifying a new file name manually (in the Virtual Disk Image column), the file name in the status window shows as the default name-disk001 and extension (.OVA filename-disk001 and .VMDK extension) instead of the new name and extension (.VDI for example). The appliance correctly imports with the new file name and extension (.VDI file in my case) so the bug is just the status window (file name & extension for the import). The attached screenshot shows the status window displaying the original (Windows 10.OVA) file name-disk001 and .VMDK extension (Windows 10-disk001.vmdk) despite the fact that a .VDI file with a new name was correctly generated as specified (Windows 10.vdi) in my session.
comment:2 by , 7 years ago
I'm not sure how you managed to get a VDI in an OVA, because the OVA specification talks explicitly about VMDK files.
Maybe it's a VMDK and you have file extensions hidden and it's actually "Windows10.vdi.vmdk", but you only see the "Windows10.vdi" part?
Again, it should not be possible to include an HD in VDI format if you export your VM to an OVA.
comment:3 by , 7 years ago
Unfortunately my file extensions are not hidden. I realize that .vmdk is what users are supposed to create from OVA, but I just tried manually entering .vdi to see what would happen. Surprisingly a .vdi file was exported, and it works.
comment:4 by , 7 years ago
Can you provide a step-by-step guide on how to manage this "feat"? You just unpacked an OVA, added a VDI and repacked the whole thing?
.VMDK file extension shows instead of .VDI as specified in appliance import wizard