#3021 closed defect (duplicate)
VBoxManage fails converting .vdi images to .vmdk
回報者: | Manolo | 負責人: | |
---|---|---|---|
元件: | VMM | 版本: | VirtualBox 2.2.2 |
關鍵字: | 副本: | ||
Guest type: | other | Host type: | Linux |
描述
The command line order for converting vdi into vmdk images, generates an image unusable with vmware (vmplayer message is: ASSERT [...]/disk.c:3868 bugNr=21838).
# VBoxManage internalcommands converthd -srcformat VDI -dstformat VMDK file.vdi file.vmdk
But converting the same file to raw and then converting into vmdk produces good images.
# VBoxManage internalcommands converttoraw file.vdi file.raw # VBoxManage convertfromraw -format VMDK file.raw file.vmdk
附加檔案 (1)
更動歷史 (7)
comment:2 16 年 前 由 編輯
Can you try this with a flat VMDK image too (2.2.x only)? It requires more space, but it'd allow to track down the bug relatively easily. Just specify --variant fixed. The resulting x-flat.vmdk files should be identical (if not, tell me), as they're the raw image data. The x.vmdk files are regular text files, so if you could attach them I wouldn't need sample files to track down this weird issue.
comment:4 16 年 前 由 編輯
I also have this issue, Virtualbox 3.0.0. I get the same assertion when I create a VMDK using:
VBoxManage clonehd Hardy\ 32.vdi Hardy\ 32.vmdk --format vmdk
I tried creating a flat VMDK, but VMware Fusion 2.0.5 won't import it and pops up an error "The file specified is not a virtual disk". The command was
VBoxManage clonehd Hardy\ 32.vdi Hardy\ 32.vmdk --format vmdk --variant fixed
I'll attach the resulting vmdk.
Can confirm this problem. Bug still exists in 2.2.2 (Host: Linux 64bit)