virtualbox.org

Windows server 2016 VM crashes repeatedly on Win server 2019 host

Virtual box version is 6.1.16
Can Somebody please suggest a solution as i am unable to even go to the login page sometimes.

Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Where did this VM come from?

What kind of drive is host drive G: ?

Why is the VM using a VHD format drive? If the VM keeps crashing then you DEFINITELY don't want to be using VHD.

That said, I don't see any sign of a VM crash. The guest OS is being shut down. So I need to ask again, where did this VM come from? I'm betting it wasn't installed as a VirtualBox VM.

mpack wrote:Where did this VM come from?

What kind of drive is host drive G: ?

Why is the VM using a VHD format drive? If the VM keeps crashing then you DEFINITELY don't want to be using VHD.

That said, I don't see any sign of a VM crash. The guest OS is being shut down. So I need to ask again, where did this VM come from? I'm betting it wasn't installed as a VirtualBox VM.

Hi, I used Virtual hard disk option while installing the guest OS.
If it is because of that how can I Change to VDI without losing any files and settings.
And the host OS is win server 2019 and the guest OS is Win Server 2016, Is that a problem?

I am not saying that the current problem is caused by using the VHD format, I simply noted it while viewing the log. Since there is no evidence of a VM problem in the log I have no idea what causes it.

And no, the fact that the guest OS is one version of Windows and the host OS is another is not a problem. If it was then there would be some evidence of a problem for the VM in the log, and there is none. I don't think you have a VM problem, I believe you have a guest OS problem, which is why I wanted to verify whether this VM was created in VirtualBox - as that is the only way to be sure that it's compatible with VirtualBox.

If the guest OS is crashing, and if that means BSOD, then it would be useful to have details of the BSOD. See How to Record BSOD Information from Windows Guests.

mpack wrote: If the guest OS is crashing, and if that means BSOD, then it would be useful to have details of the BSOD.

The Guest OS was created in the Virtual box itself and I for once believed that the Guest OS is crashing because of the VM.
I do get a BSOD and the error code shows Watchdog Violation.

That is a pretty common problem in Server 2016, not just in vms. Did you bing/google watchdog violation windows 2016? Is it a domain controller?

BillG wrote:That is a pretty common problem in Server 2016, not just in vms. Did you bing/google watchdog violation windows 2016? Is it a domain controller?

Yeah sadly its a domain controller, I believe it has something to do with the update. Because after BSOD and in Advance repair after we select "Last Known Good Configuration (advanced)" the system seems to be booting up fine. And upon updating windows again the same BSOD loop begins.