@fx991 You cannot live-migrate between hosts with processors that have different instruction sets.

You would have to shut down the VM and then migrate it and then power it back on after migration completes.

The E5506 and E5620 have similar instruction sets but the E5506 does not support hyperthreading or AES instructions, so there are some differences here.

The E5-2643 v2 is completely different.

If you power off your VM and then migrate it, it should be fine. From what I understood from your post you tried to live-migrate it and then reboot it after it had migrated and run into issues, which I would expect to happen.

@BenjiReis Thanks! I was looking in host-view and couldn't find this.

@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.

@dinhngtu Same problem on a fresh install.

@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.

@dinhngtu Is there any special process for installing these, or is it just installing all of the RPM's one at a time?

@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?

@guiltykeyboard Both of my hosts are identical

@dinhngtu Dell R660 with 2x Intel(R) Xeon(R) Gold 5416S

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.

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.