Server 2016 BSOD Loop
-
On 11/12, one of my Server 2016 VM's got stuck in a boot loop.
It starts, and then has a BSOD with the code KMODE Exception Not Handled.
Taking the VHD from our storage server and copying it to a Hyper-V server allows it to boot. The issue seems to be with XCP-NG.
My two hosts are XCP-NG 8.3.0 with the latest patches applied. I've had this VM for a few years - and it seemed fine after the migration to 8.3.0 - until it wasn't. None of our other VM's have this issue.
This VM has secure boot disabled and does not have a VTPM. There are no passthrough PCI or USB devices.
-
-
Additionally, I just did a fresh install of Server 2016 in a new VM and experienced the exact same code as soon as the VM finished the OS install and rebooted the first time with no drivers or anything.
Seems to be an issue with Server 2016 VM's.
-
Could you describe the hardware being used?
-
@dinhngtu Dell R660 with 2x Intel(R) Xeon(R) Gold 5416S
-
@guiltykeyboard Both of my hosts are identical
-
I think it's a compatibility problem with newer Intel CPUs. We have some experimental patches available. Do you have an identical host for testing purposes? Could you install the following RPMs and see if it helps?
https://nextcloud.vates.fr/index.php/s/MYZpPgQCRwWnDYq
If you don't want to install test RPMs you could try the following command instead:
xe vm-param-add uuid=... param-name=platform msr-relaxed=true -
@dinhngtu I can run all of my VM's on one host while testing on the other.
Which of the two methods should I try first?
-
Please try the RPMs first, they contain the fixes that we'd like to integrate with Xen upstream. Also please note that you need to reboot the host after installing these patches.
-
@dinhngtu Is there any special process for installing these, or is it just installing all of the RPM's one at a time?
-
You can use the following command:
yum localinstall xen-{dom0-libs,dom0-tools,hypervisor,libs,tools}-4.17.5-4.0.lbr.19.xcpng8.3.x86_64.rpm -
@dinhngtu said in Server 2016 BSOD Loop:
yum localinstall xen-{dom0-libs,dom0-tools,hypervisor,libs,tools}-4.17.5-4.0.lbr.19.xcpng8.3.x86_64.rpm
Installing those RPMs, restarting the host, and then starting the 2016 VM on that host did not fix the issue. It had the same result.
One thing that was different is that it said preparing devices when starting before it hit the BSOD.
-
Could you try it again with a fresh 2016 VM? I'll try to reproduce the issue.
-
@dinhngtu Same problem on a fresh install.
-
@guiltykeyboard This was not an issue on 8.2.* and when we originally upgraded to 8.3 it wasn't an issue either.
I think perhaps the latest round of patches might have introduced an issue.
-
Could you collect a crash dump using a boot CD?