Reboot Ubuntu18 Guest into a Fire Pit

Discussions about using Linux guests in VirtualBox.

Reboot Ubuntu18 Guest into a Fire Pit

Postby SavedStates » 7. Jul 2019, 23:21

On the reboot after allowing the Ubuntu18.04 guest to apply updates (Windows10 host, VirtualBox v6.0 with Guest additions installed) I got the following fatal error modal dialog box ...
A critical error has occurred while running the virtual machine and the machine execution has been stopped

A filter on the log file for the keyword "error" brings up this ...
00:00:02.872314 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2904000879(*) cErrors=0
00:00:02.872321 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2904002873(*) cErrors=0
00:00:02.872328 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x2 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2904002599(*) cErrors=0
00:00:02.872334 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x3 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2904002916(*) cErrors=0
00:00:27.747830 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvinitx.dll: fKeyUsage=0x0, missing 0x1: \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvinitx.dll
00:00:27.748032 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvinitx.dll): rcNt=0xc0000190
00:00:29.092780 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:29.585720 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
02:20:40.579174 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)}, preserve=false aResultDetail=0
02:20:40.583042 Error 1 Idle Fixed 0 (0x0)
02:20:40.583060 Error 1 Idle Fixed 0 (0x0)
02:20:40.590018 HM error = 0x0 (0)
02:20:40.590038 HM error = 0x0 (0)

I've been using this guest image without stability issues since I built it over a month ago; no problems EXCEPT that I cannot update it because the above fatal error kills it on the reboot after the update.

Thanks in advance for any insight.
Attachments
VBoxLog20190707-bottom-portion.log
BOTTOM 1k lines of log file at time of reboot crash
(88.87 KiB) Downloaded 10 times
VBoxLog20190707-top-portion.log
TOP part of log file at time of reboot crash
(34.56 KiB) Downloaded 10 times
SavedStates
 
Posts: 5
Joined: 23. Jul 2018, 03:42

Re: Reboot Ubuntu18 Guest into a Fire Pit

Postby socratis » 8. Jul 2019, 08:52

Please do not split your logs, it makes it really painful to work with. Instead, ZIP your log and post that.
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.
socratis
Site Moderator
 
Posts: 27259
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Reboot Ubuntu18 Guest into a Fire Pit

Postby SavedStates » 10. Jul 2019, 03:08

Sorry about splitting the log; did not realize a ZIP would have been helpful.

Looks like I no longer have the original log file on disk. Do you have any insight on what may be happening from the partials attached?
SavedStates
 
Posts: 5
Joined: 23. Jul 2018, 03:42

Re: Reboot Ubuntu18 Guest into a Fire Pit

Postby socratis » 10. Jul 2019, 09:33

SavedStates wrote:Looks like I no longer have the original log file on disk
Repeat the scenario and get a fresh log.

SavedStates wrote:Do you have any insight on what may be happening from the partials attached?
Last line of the Top part wrote:
00:00:02.819523 ********************* End of CFGM dump **********************
First line of the Bottom part wrote:
02:20:40.588195 CPU[1]: VM-exit history:
There's a lot of information missing there...

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
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.
socratis
Site Moderator
 
Posts: 27259
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to Linux Guests

Who is online

Users browsing this forum: No registered users and 8 guests