All of a sudden I'm having difficulty getting VirtualBox to run on my Mac. Its not clear to me on what I should be doing, or even looking at to get started in analyzing this issue.
Things that used to work, don't work anymore, or just work occasionally / intermittently.
-When either the Oracle VM VirtualBox Manager or the running box I keep seeing the spinning beach ball of death.
-The running box just hangs. No message, sometimes I see the Vagrant login screen (based on the box I'm using) or just a black screen.
-Sometimes I can find a log screen in the Oracle VM VirtualBox Manager, other times not. Its not clear to me on what the log system works.
-Generally the only way to clean things up is to hard button power off. (I doubt this is a good process.)
-Force Quit Applications shows "(not responding)" for VirtualBox and for VirtualBox VM. I do see that I can individually Force Quit those two applications.
It's not clear to me on what to look at when the box just hangs / halts / quits responding. Any hints on troubleshooting procedure?
Note, I'm running:
--VirtualBox 6.1.34
--MacOS Monterey Version 12.3.1
--Vagrant 2.2.19
The specific Vagrant box I'm using is "peru/ubuntu-20.04-desktop-model" a well documented Ubuntu box. It's frequently updated.
Big Picture Overview for VirtualBox Failures on MacOS?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Big Picture Overview for VirtualBox Failures on MacOS?
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Note however that we do not support Vagrant here.
Note however that we do not support Vagrant here.
Re: Big Picture Overview for VirtualBox Failures on MacOS?
Here's that log file. It's an Ubuntu desktop box.
I opened up the virgin box. It worked just fine. I logged in, went thru the welcome screens. At the end, it asked me if I wanted to update software. I said yes. It did the update, then asked for a reboot. The reboot just gets hung up. Fail. Many thanks.
I opened up the virgin box. It worked just fine. I logged in, went thru the welcome screens. At the end, it asked me if I wanted to update software. I said yes. It did the update, then asked for a reboot. The reboot just gets hung up. Fail. Many thanks.
- Attachments
-
- Vbox.log.zip
- --VirtualBox 6.1.34. --MacOS Monterey Version 12.3.1. --Ubuntu Desktop content
- (32.74 KiB) Downloaded 6 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Big Picture Overview for VirtualBox Failures on MacOS?
This part is not good - memory over-commitment.
Next error is that you have "foreign" Guest Additions installed. These are not controlled by the Oracle devs and so are not guaranteed to work, nor in fact are they supported at all.
CPU is likewise over-committed:00:00:01.472913 Host RAM: 16384MB (16.0GB) total, 8054MB (7.8GB) available
...
00:00:01.577735 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)
Reduce to 2 cores.00:00:01.816676 CPUM: Physical host cores: 4
...
00:00:01.577730 NumCPUs <integer> = 0x0000000000000004 (4)
Next error is that you have "foreign" Guest Additions installed. These are not controlled by the Oracle devs and so are not guaranteed to work, nor in fact are they supported at all.
The version number of the genuine article does not include that "_Ubuntu" modifier. Install the genuine GAs bundled with the software.00:00:15.374009 VMMDev: Guest Additions information report: Version 6.1.26 r145957 '6.1.26_Ubuntu'
Re: Big Picture Overview for VirtualBox Failures on MacOS?
MPack... thx for your prompt reply.. Let me do some digging. Again, many thanks.