Hi
I have a Windows 2019 server guest running on a Debian Linux 10 host, which is (for a month or so) repeatedly crashing and immediately restarting, the vbox-session just goes on. Before it was running without any problems for about 2 years.
Attached I upload the vbox.log for the ongoing session. Windows is saying that there have been unplanned shutdowns (translated to vbox.log-timestamps) at 08:41:* and 58:24:*
VBox version 6.1.30, guest additions 6.1.30, extension pack 6.1.32
Has anyone an idea if this could be a VirtualBox problem?
In Windows I was searching and trying a lot of options, without success so far, so maybe it is in vbox?
Schogol
Windows 2019 Server-guest repeatedly crashing and immediately restarting
Windows 2019 Server-guest repeatedly crashing and immediately restarting
- Attachments
-
- TH-SVR_2023-03-02_vbox.log
- (115.99 KiB) Downloaded 2 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 2019 Server-guest repeatedly crashing and immediately restarting
There's a mismatch between Virtualbox and Extension Pack:
Looks like you might have tried an RDP session about 11 hours in, that may have failed. The EP mismatch might be he cause of that.
The VM was started from a saved state:
The above may not be influencing the VM OS, though. The VM OS reported two BSODs:
The "P0" numbers are the BSOD stop codes, 3b and 1e. These can be investigated using Microsoft help channels. If the solutions show RAM issues, try a host RAM test.
EP should match Virtualbox version, https://www.virtualbox.org/wiki/Download_Old_BuildsVirtualbox and Extension Pack versions:
00:00:00.029523 VirtualBox VM 6.1.30 r148432 linux.amd64 (Nov 22 2021 15:39:16) release log
00:00:00.041385 Installed Extension Packs:
00:00:00.041399 Oracle VM VirtualBox Extension Pack (Version: 6.1.32 r149290; VRDE Module: VBoxVRDP)
Looks like you might have tried an RDP session about 11 hours in, that may have failed. The EP mismatch might be he cause of that.
The VM was started from a saved state:
Logs show better diagnostic info when starting from full shutdown, not saved state.00:00:00.042486 Console: Machine state changed to 'Restoring'
The above may not be influencing the VM OS, though. The VM OS reported two BSODs:
The VM 'hardware' keeps running, so there's no Virtualbox issues visible so far in running the VM.08:41:09.457994 GIM: HyperV: Guest indicates a fatal condition! P0=0x3b
58:24:05.977892 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e
The "P0" numbers are the BSOD stop codes, 3b and 1e. These can be investigated using Microsoft help channels. If the solutions show RAM issues, try a host RAM test.
Re: Windows 2019 Server-guest repeatedly crashing and immediately restarting
@scottgus1
Wow, thank you very much, that is more I could expect!
I knew about the extension pack mismatch, but as the extension pack is newer, I did not see a problem in that. But now I changed it so it fits the other packages.
Now I'll investigate the P0 codes as you suggested and try to find out more that way.
Thanks again, you helped a lot!
Wow, thank you very much, that is more I could expect!
I knew about the extension pack mismatch, but as the extension pack is newer, I did not see a problem in that. But now I changed it so it fits the other packages.
Before the savestate and restore events the VM was just running about an hour after a fresh start from scratch, and as I met lots of events of the P0=... kind before, I am pretty sure the log says the right things.The VM was started from a saved state:
Logs show better diagnostic info when starting from full shutdown, not saved state.
Now I'll investigate the P0 codes as you suggested and try to find out more that way.
Thanks again, you helped a lot!