Opened 7 years ago
Closed 5 years ago
#17833 closed defect (obsolete)
OVF export of virtualbox image using vmdk disk fails.
| Reported by: | jalbers | Owned by: | |
|---|---|---|---|
| Component: | OVF | Version: | VirtualBox 5.2.12 |
| Keywords: | Cc: | ||
| Guest type: | BSD | Host type: | other |
Description
Using VirtualBox Version 5.2.12 r122591
Exporting a good vbox appliance with a vmdk disk via the GUI generates an error. Doing the same thing via the command line gives the same error, plus some additional info.
There is a vbox named 'server1' with one disk image 'server1.vmdk'. At creation chose vmdk to make it possible to read the image with VMware if problems arose.
c:\Users\joe\VirtualBox VMs\server1>vboxmanage export server1 -o c:\VM\server1.ova --ovf10 0%... Progress state: VBOX_E_FILE_ERROR VBoxManage.exe: error: Appliance write failed VBoxManage.exe: error: Could not create the exported medium 'server1-disk001.vmdk' (VERR_INVALID_PARAMETER) VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium VBoxManage.exe: error: Context: "enum RTEXITCODE cdecl handleExportAppliance(struct HandlerArg *)" at line 1263 of file VBoxManageAppliance.cpp
I took a brief look at the sources and there wasn't any immediate resolution.
For this case, there is a workaround, which might give hints for the underlying issue:
- Clone the vmdk disk.
c:\Users\joe\VirtualBox VMs\server1>VBoxManage clonehd --format VDI server1.vmdk server1.vdi 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
- In the server1 settings, remove the vmdk disk and add the vdi disk.
- Boot server1 to confirm that it runs correctly with the vdi disk.
- Export the server1 machine to an ova file using the GUI Export Appliance... tool.
Change History (2)
comment:1 by , 7 years ago
comment:2 by , 5 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
No response and no logs provided, closing as obsolete.
Please attach the VBoxSVC.log, the .vbox config of the VM which fails to export and more information about the disk image used. It looks like you are using a 2GB split VMDK, in that case please attach the server1.vmdk too (it should be really small).