[Solved] Critical error on boot

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
Jokinha
Posts: 4
Joined: 15. Jan 2018, 14:34

[Solved] Critical error on boot

Post by Jokinha »

Hello
I wanted to install Kali Linux in VM what I did with no problems.
The first thing I did after the installation was completed was update it with the following command in terminal:

Code: Select all

apt-get update && apt-get upgrade && apt-get dist-upgrade
Everything run cool with no errors. However, when I rebooted the system I got a critical error.

The log file is too big to attach here, so I will copy the first paragraphs log:

Code: Select all

VirtualBox VM 5.1.30 r118389 darwin.amd64 (Oct 16 2017 11:53:21) release log
00:00:02.887404 Log opened 2018-01-15T12:35:06.526221000Z
00:00:02.887406 Build Type: release
00:00:02.887423 OS Product: Darwin
00:00:02.887431 OS Release: 16.7.0
00:00:02.887439 OS Version: Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64
00:00:02.887576 DMI Product Name: MacBookPro7,1
00:00:02.887653 DMI Product Version: 1.0
00:00:02.887665 Host RAM: 6144MB (6.0GB) total, 3390MB (3.3GB) available
00:00:02.887669 Executable: /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
00:00:02.887669 Process ID: 11718
00:00:02.887670 Package type: DARWIN_64BITS_GENERIC
00:00:02.890635 Installed Extension Packs:
00:00:02.890656   Oracle VM VirtualBox Extension Pack (Version: 5.1.30 r118389; VRDE Module: VBoxVRDP)
00:00:02.893168 Console: Machine state changed to 'Starting'
00:00:02.895091 Qt version: 5.6.3
00:00:02.932252 SUP: Loaded VMMR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:02.934171 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:03.030134 Guest OS type: 'Debian_64'
00:00:03.064536 fHMForced=true - No raw-mode support in this build!
00:00:03.123548 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:03.166944 File system of '/Users/joaosacramento/VirtualBox VMs/Kali Linux/Snapshots' (snapshots) is unknown
00:00:03.166968 File system of '/Users/joaosacramento/VirtualBox VMs/Kali Linux/Kali Linux.vdi' is hfs
00:00:03.224961 Shared clipboard service loaded
00:00:03.224988 Shared clipboard mode: Off
00:00:03.230880 Drag and drop service loaded
00:00:03.230905 Drag and drop mode: Off
00:00:03.236461 Guest Control service loaded
00:00:03.248354 ************************* CFGM dump *************************
Does anyone knows why I'm getting this error?
Last edited by socratis on 15. Jan 2018, 15:49, edited 1 time in total.
Reason: Marked as [Solved].
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error on boot

Post by socratis »

Partial logs are not that helpful I'm afraid. You should ZIP and attach the full log. See the "Upload attachment" tab below the reply form. But for the moment, that's not necessary. If you had said "I'm using VirtualBox 5.1.30", that would have been enough.

If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. As of this writing, that would be version 5.2.4. If that doesn't work you should try the latest test builds, especially with all the Spectre/Meltdown patches coming in from all sides. If you still want to stick to the 5.1.x series, then the 5.1.x test builds should contain the fixes as well.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Jokinha
Posts: 4
Joined: 15. Jan 2018, 14:34

Re: Critical error on boot

Post by Jokinha »

Hey, it worked, thank you very much :)
Last edited by socratis on 15. Jan 2018, 15:48, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Critical error on boot

Post by socratis »

Great, thanks for the feedback. Marking as [Solved].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply