[Bug]: VBoxManage cannot identify a VMDK. #527
Description
Version
7.2.6
Host OS Type
macOS (Darwin)
Host OS name + version
macOS Sequoiia 15.7.2
Host Architecture
x86
Guest OS Type
Windows
Guest Architecture
x86
Guest OS name + version
Windows 10 build ? (it is up to date)
Component
VBoxManage CLI
What happened?
I attempted to clone a VMDK file to VDI so it could be compacted. It could not identify the file as VMDK format. Below is the result.
I performed the same operation on a linux host on the same file. Same problem
.
I performed the same operation on a linux host for a different Windows guest. Same VB version, no problem.
The VMDK file is the primary file for the Windows host and there is no issue loading, using, updating, or saving that file.
Is VDI the preferred format?
A confusion factor: The file size is 65 GB, Windows reports that 128 GB are used. Why the difference? Compression?
$ ll
total 65G
-rw-r--r-- 1 jmoe users 65G Feb 2 18:38 win10-64-disk002.vmdk
$
$ VBoxManage clonemedium win10-64-disk002.vmdk win10-64-disk002.vdi disk --format=VDI
VBoxManage: error: Could not get the storage format of the medium '/data02/tmp/win10-64-disk002.vmdk' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 197 of file VBoxManageDisk.cpp
$
How can we reproduce this?
Well... I could upload the VMDK file. It is 65 GB and would take a goodly amount of time, about 35 hours. (Our upload speed is 5Mbps.)
Did you upload all of your necessary log files, screenshots, etc.?
- Yes, I've uploaded all pertinent files to this issue.