Opened 12 years ago
Closed 12 years ago
#11808 closed defect (fixed)
OVA Import Failed when changing VM named from "vm" => Fixed in SVN
Reported by: | superponible | Owned by: | |
---|---|---|---|
Component: | OVF | Version: | VirtualBox 4.2.8 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
I was attempting to import an OVA. The Virtual Appliance name within the OVA was "vm". For this example, I changed the name from "vm" to "NEWNAME" before importing. When I clicked Import, I got an error saying it "Could not find a valid medium format for the target disk", and the disk name it listed had had the extension changed from vmdk to NEWNAMEvmdk.
The full error is pasted below. The OVA I was using was for REMNUX available here: http://zeltser.com/remnux/#download-remnux
Failed to import appliance C:\Users\<username>\VMs\ISOs\remnux-4.0-ovf-public.ova.
Could not find a valid medium format for the target disk 'C:\Users\<username>\VirtualBox VMs\NEWNAME\remnux-4.0-ovf-public-disk1.NEWNAMEdk'.
Result Code: VBOX_E_NOT_SUPPORTED (0x80BB0009) Component: Appliance Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}
Attachments (1)
Change History (6)
by , 12 years ago
Attachment: | vbox-error.PNG added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Confirmed the issue, you can workaround this by using "VBoxManage import <ova path> --vsys 0 --vmname NEWNAME".
comment:4 by , 12 years ago
Summary: | OVA Import Failed when changing VM named from "vm" → OVA Import Failed when changing VM named from "vm" => Fixed in SVN |
---|
Fix is part of VBox 4.3 Beta 2. Please give it a try!
comment:5 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I said in the text it was renamed to "NEWNAMEvmdk", but the copied error shows the correct renaming to "NEWNAMEdk".