Crashing on startup - 4.14.0-kali3-amd64 (kali1 starts fine) (#17346)

[Bard]

---

[ModEdit; related ticket: #17436]

Please update your VirtualBox installation to the latest test build: ≥120181 (5.2.x) or ≥120178 (5.1.x).

---

Hello, I ran a dist-upgrade this morning, and attempted to reinstall the Guest Additions on my Kali distro. The Guest additions failed to install because it was missing the headers, so I tried installing the kali3-amd64 headers.

Unfortunately, after restarting the system, I immediately get a crash whenever I select kali3 (even recovery mode). As stated in the subject, kali1 starts just fine, but I can't install the guest additions, meaning I'm stuck at 800x600 resolution.

Here's the relevant part of the log:

Code: Select all

00:01:00.625436 Port 01 (USB2): PORTSC:    206A1: CCS PLS=5 PP SPD=1 CSC
00:01:00.625438 Port 02 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625439 Port 03 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625440 Port 04 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625441 Port 05 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625442 Port 06 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625443 Port 07 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625444 Port 08 (USB2): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625445 Port 09 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625446 Port 10 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625447 Port 11 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625448 Port 12 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625449 Port 13 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625461 Port 14 (USB3): PORTSC:      2A0: PLS=5 PP SPD=0
00:01:00.625463 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:00.625531 emR3Debug: rc=VERR_PGM_INVALID_CR3_ADDR

Anyone else experiencing this with kali3?

[socratis]

Take a look at https://www.virtualbox.org/ticket/17436
There seems to be a barrage of errors with updated Linux guests and VERR_PGM_INVALID_CR3_ADDR Guru Meditations really lately...

[Bard]

Thanks, looks like it's already been fixed in an internal build (r70948).

[socratis]

Fixed in r70498 (internally 120115)

So, unless you see a test build (or a release) with a revision greater than 120115, you'd have to compile VirtualBox from sources.

[bird]

We've put out some new test builds which should include the fix for this issue. Enjoy.
-bird

[socratis]

Please update your VirtualBox installation to the latest test build: ≥120181 (5.2.x) or ≥120178 (5.1.x).

[Bard]

Fix confirmed with r120181.