Server 2016 BSOD Loop
-
@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?