socratis wrote:How did you manage to get that .vbox file?
Code: Select all
$ cd /home/susu/VirtualBox VMs/W10/
zip W10.zip W10.vbox
socratis wrote:There's a whole section missing from the beginning, the "<MediaRegistry>" one, plus the "<Display> one.
No idea. I'm not a vbox expert
What I can tell is that the other VMs do not have such a section either and they all just run fine. So IMO, that can't be the culprit.
socratis wrote:Could you clarify what you did?
The VM freezed. So I've restarted the VM service and now the VM does no longer boot.
socratis wrote:Also, post the output of the commands:
Sure
Code: Select all
$ VBoxManage showmediuminfo {c3a8c01f-80c0-4619-ab28-1f0ea8074a56}
UUID: c3a8c01f-80c0-4619-ab28-1f0ea8074a56
Parent UUID: 5b0753af-a3ba-49ac-8745-5e1d8ed73dbc
State: created
Type: normal (differencing)
Auto-Reset: off
Location: /home/susu/VirtualBox VMs/W10/Snapshots/{c3a8c01f-80c0-4619-ab28-1f0ea8074a56}.vdi
Storage format: VDI
Format variant: differencing default
Capacity: 500000000 MBytes
Size on disk: 1909 MBytes
Encryption: disabled
$ VBoxManage showmediuminfo {7610546f-7140-4d7c-bb04-0ee669708885}
VBoxManage: error: The given path '{7610546f-7140-4d7c-bb04-0ee669708885}' is not fully qualified
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
$ VBoxManage showmediuminfo {5b0753af-a3ba-49ac-8745-5e1d8ed73dbc}
UUID: 5b0753af-a3ba-49ac-8745-5e1d8ed73dbc
Parent UUID: 4a4dcb3a-9827-4962-b1b6-c6be448d6e39
State: created
Type: normal (differencing)
Auto-Reset: on
Location: /home/susu/VirtualBox VMs/W10/Snapshots/{5b0753af-a3ba-49ac-8745-5e1d8ed73dbc}.vdi
Storage format: VDI
Format variant: differencing default
Capacity: 500000000 MBytes
Size on disk: 2292 MBytes
Encryption: disabled
Child UUIDs: 70ced5db-510a-47d1-97de-5d68e148e8b1
f3aad71d-1de4-4ee7-a02d-f2466006dd28
c3a8c01f-80c0-4619-ab28-1f0ea8074a56
socratis wrote:And please explain to me why I don't see a "/home/susu/VirtualBox VMs/W10/W10.vdi"
No idea either. I suspect it's because I've created the VM initially with
--mtype immutable. Anyway, I see that the other vms do not have such a VDI file either and they all just run fine. So IMO, that can't be the culprit.