100% CPU time followed by system reboot

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
onehundred
Posts: 2
Joined: 16. Dec 2015, 07:11

100% CPU time followed by system reboot

Post by onehundred »

Code: Select all

Virtualbox: 5.0.10 r104061
Host: OS X 10.11.2 (64-bit)
Guest: Kali Linux (64-bit) & Alpine Linux (64-bit)
Having an issue where once a VM is started it consumes 100% CPU and then forces a system reboot. Killing the "Virtualbox VM" process results in a reboot as well.

How do I approach fixing this issue?
Attachments
VBox.zip
(6.41 KiB) Downloaded 9 times
onehundred
Posts: 2
Joined: 16. Dec 2015, 07:11

Re: 100% CPU time followed by system reboot

Post by onehundred »

Alright, I solved this while sleeping :)

In case it helps anyone else, I had run

Code: Select all

sudo nvram boot-args=-no_shared_cr3

and after running

Code: Select all

sudo nvram -d boot-args

and rebooting Virtualbox started working as expected.
loukingjr
Volunteer
Posts: 8851
Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: just about all that run

Re: 100% CPU time followed by system reboot

Post by loukingjr »

Not trying to be mean or embarrass this user but this post is nonsense.
the first command…

Code: Select all

sudo nvram boot-args=-no_shared_cr3
Has nothing to do with running VMs and was used to try and thwart zero-day exploits. It also causes a performance hit on the system. This has already been addressed in OSX 10.11.2
The second command isn't even the correct syntax.

Lastly, CPU time is not measured by a percentage.

If I were an OSX user, which I am, I certainly wouldn't run the commands.

Just to add, I have a Kali 2.0 guest, it's CPU Use is 3% on average and certainly never caused a system reboot. It's just a Debian based distro.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
Post Reply