VM Computers

VM Computers

156k Downloads

HD issue x2

undonecroissant opened this issue ยท 7 comments

commented

I have a hd that is saying I don't have enough space (which isn't accurate). When I click on the (reformat?) hard drive, I get brought back to the launcher screen. Please advise. I am running 1.16.3. Let me know if you need more information. I also already deleted the setting in the VB application and in the VM folder. Thank you.

Screen Shot 2020-12-12 at 6 36 57 PM

crash-2020-12-12_18.18.23-client.txt

commented

Should I need to know, it says you have macOS 10.15.7. That's Catalina innit?
Try VirtualBox 6.1.14. That's what I use. I do it on Windows 10, don't have much experience with macOS other than in the Apple Store and school computers ๐Ÿ˜‰

commented

Does it say "not enough space" no matter what you type in it?

commented

@Delta2Force Yes, it says that no matter what number I put in. I was able to find the folder for the HD and just delete what was is it. @Busaruba2011 I'll try that and report back. Thank you.

commented

I am using VB 6.1.14. That wasn't working. I kept getting a
com.apple.TCC
0x00007fff64a0b59f CRASHING_DUE_TO_PRIVACY_VIOLATION + 163 e
error. If I sudo VirtualBox though, the system seems to work. I don't understand why that makes a difference, but my machine is now working.

commented

Huh.

commented

I am using VB 6.1.14. That wasn't working. I kept getting a
com.apple.TCC
0x00007fff64a0b59f CRASHING_DUE_TO_PRIVACY_VIOLATION + 163 e
error. If I sudo VirtualBox though, the system seems to work. I don't understand why that makes a difference, but my machine is now work

@undonecroissant i found this https://developer.apple.com/forums/thread/659732
Someone said in a terminal, type 'sudo virtualbox'

commented

I am using VB 6.1.14. That wasn't working. I kept getting a
com.apple.TCC
0x00007fff64a0b59f CRASHING_DUE_TO_PRIVACY_VIOLATION + 163 e
error. If I sudo VirtualBox though, the system seems to work. I don't understand why that makes a difference, but my machine is now working.

Try starting the VM from VirtualBox (and allow privacy options if required) and see if it works