[WorksForMe] Mac Install Corrupt all of a sudden?

[dstyp]

I'm on a 2015 Macbook Pro 15" with 10.13.6. Been running Win10 in a Vbox for a while.

Suddenly guest additions stopped working. No mounting available. Copy paste wouldnt work between systems either. Despite all of these options being activated.

Noticed that Win10 couldnt update due to needing more space. Looked up how to create more space.

Commands:

ds-MBP15:~ root# VBoxManage showhdinfo '/Users/dave/VirtualBox VMs/Windows 10/Windows 10.vbox'
VBoxManage: error: Could not get the storage format of the medium '/Users/dave/VirtualBox VMs/Windows 10/Windows 10.vbox' (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 179 of file VBoxManageDisk.cpp
ds-MBP15:~ root#

This implies that the installation has been corrupted. Did my install become corrupt of a sudden???

Attaching log for reference.

[socratis]

When doing the "VBoxManage showhdinfo 'path to vbox'"

You're not supposed to have a 'path to vbox', you're supposed to have a 'path to vdi'.

Always post exact command input/output/error. Do not try to translate/interpret/obfuscate it, because things get "Lost in translation".

[dstyp]

I apologize deeply for my mistake. I've updated the original post to reflect what I was "supposed" to do initially.

Again, I apologize.

[socratis]

Did my install become corrupt of a sudden???

No, not at all. What happened is that you didn't issue the command correctly, or I should say, you didn't issue the command as the appropriate user:

root# VBoxManage showhdinfo '/Users/dave/VirtualBox VMs/Windows 10/Windows 10.vbox'

VirtualBox registers and runs in the context of each user. So, user A can't have access to the VMs (or the VDIs) of user B. That includes 'root'. Becoming 'root', 'admin' or anything else than the user that uses the VMs, won't be able to see the VMs.

What you need to do is to issue the same command as 'dave'. Not as 'root'. Being 'root' doesn't give you additional powers, not in the context of VirtualBox anyway. Don't switch users, be yourself.

I apologize deeply for my mistake.

Don't sweat it!
It's just a thing to remember, that accurate reporting leads to the solution much faster/accurately...

[dstyp]

Thanks for the reply.

Same commands issued as my user (dave) yields the same result:

~ VBoxManage showhdinfo '/Users/dave/VirtualBox VMs/Windows 10/Windows 10.vbox'
VBoxManage: error: Could not get the storage format of the medium '/Users/dave/VirtualBox VMs/Windows 10/Windows 10.vbox' (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 179 of file VBoxManageDisk.cpp
~

[andyp73]

Same commands issued as my user (dave) yields the same result:

You now need to go back and read the original reply from Socratis:

You're not supposed to have a 'path to vbox', you're supposed to have a 'path to vdi'.

Try:

VBoxManage showhdinfo 'Users/dave/VirtualBox VMs/Windows 10/Windows 10.vdi'

-Andy.

[dstyp]

There we go. Thanks for the patience and help!

[socratis]

D'oh! I was so distracted by the "root", that I didn't even notice the .vbox at the end. Thanks Andy for catching that...

Marking as [WorksForMe].