Page 1 of 1
Virtual Machine not start
Posted: 8. Mar 2016, 10:55
by matrixmi
After update VirtualBox to version 5.0.16r105871 I'm not able to open my Virtual Machine and I received this error:
Code: Select all
VD: error VERR_NOT_SUPPORTED opening image file '/home/dario/VM/md1fj1bc/md1fj1bc.vmdk' (VERR_NOT_SUPPORTED).
Codice 'uscita: NS_ERROR_FAILURE (0x80004005)
Componente: ConsoleWrap
Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Workaround: Only disable USB controller or using USB 1.1 Virtual Machine start properly.
Any ideas for solve this problem?
Thanks
Re: Virtual Machine not start
Posted: 8. Mar 2016, 11:34
by mpack
It means there's something wrong with the VMDK. You'd have to find out what that is and fix it.
Usually this happens with multipart variants of VMDK when you don't have all the parts. It could also mean a corrupted header, or the file isn't a VMDK at all, despite the extension.
See if you can do an MD5 checksum comparison on the file set.
Re: Virtual Machine not start
Posted: 8. Mar 2016, 11:50
by matrixmi
ok, how i can perform an MD5 comparison?
thanks
Re: Virtual Machine not start
Posted: 8. Mar 2016, 12:46
by mpack
Google for that.
Re: Virtual Machine not start
Posted: 8. Mar 2016, 14:58
by matrixmi
yes, normally I use MD5 comparison for other activities but, unfortunately, it's not clear to me how to use it (MD5) in this contest.
What's the string to compare?
Re: Virtual Machine not start
Posted: 8. Mar 2016, 16:33
by mpack
I can't tell you that without knowing how the file set was distributed. Usually it's as installer, or an archive. Either way it's possible for the originator to provide md5 checksums of the files which you can compare against the checksum of your downloaded copy.
Since you are using a VMDK, and it is corrupted, I'm assuming that an OVA/OVF or similar download or USB stick transfer is involved somehow. Either way you have working state A, and communications medium leading to non working state B. Compare the checksums of A and B (pre installation).