[FIXED IN SVN] VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation

[GregB3]

I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows:

A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on ​https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows)

I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out:

00:00:17.401353 !! VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)

I am attaching a .ZIP file of the VBox.log.

[GregB3]

log file

[Socratis]

Another one with "VERR_PGM_INVALID_CR3_ADDR", after an updated Linux kernel in the forums: ​https://forums.virtualbox.org/viewtopic.php?f=3&t=86183

[bird]

Reproduced it. The bug is specific to VT-x without nested paging, i.e. older cpus. Should be simple to fix, but some patience might be needed before we get a chance to put out a build that includes it...

[Socratis]

@bird
Just FYI:

• The 1st log from GregB3 (here) shows a "Core2 Duo CPU E8400 @3.00GHz".
• The 2nd log from Barb (​linked above) shows an "i5-5300U CPU @2.30GHz".
• The 3rd log from ​aspicer shows a "Core2 Duo CPU E8400 @3.00GHz".

[Socratis]

I forgot the one from #17441 with a "Core2 Quad CPU Q9450 @2.66GHz".

[bird]

Fixed in r70498 (internally 120115).

[bird]

We've uploaded test builds for 5.1.x and 5.2.x that should include the fix.