Got the Blue screen from a VM.... Tried to install Windows 2019 Server and got the blue screen, not sure what logs to look at to:

 

It said stop code: kmode exception not handled

 

what kind of system do you use? AMD or Intel? VNC or with a GPU passed through. Let see the xml for the vm...etc...

My Bad

Model: Custom

M/B: ASUSTeK COMPUTER INC. ROG CROSSHAIR VIII HERO (WI-FI) Version Rev X.0x - s/n: 190856413301420

BIOS: American Megatrends Inc. Version 0803. Dated: 08/01/2019

CPU: AMD Ryzen 9 3900X 12-Core @ 3800 MHz

HVM: Enabled

IOMMU: Enabled

Cache: 768 KiB, 6144 KiB, 65536 KiB

Memory: 64 GiB DDR4 (max. installable capacity 128 GiB)

Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mbps, full duplex, mtu 1500
 eth1: interface down

Kernel: Linux 5.7.8-Unraid x86_64

 

This is a qemu 5.0 bug with ryzen. Try changing from host-passthrough to host-model in your xml. There is another way to fix this bug it requires some qemu args added to the end of your xml but I'm not at home to give them to you but they work for sure. 

thanks, and thing helps

 

@ernestp I had the same issue caused by Kaspersky Internet Security installed inside the VM. By default KIS checks if any virtualisation features are available and try's to use it. Any time i tried to change some settings in KIS or even uninstalling it, it will crash the VM. I couldn't even dissable this function. Changing it to "host-model" or to "custom" allowed me to dissable this feature in Kaspersky. I guess for you there are features like Hyper-V enabled which sees some CPU features from the host system and tries to use them. Try to dissable Hyper-V if you don't need them or use the "custom"  or "host-model" cpu flag.

Hello,

I just installed the trial version 6.9 beta 25 on my new Ryzen 9 3900X with MSI X570 Tomahawk Wifi mainboard.

Just created a WIN10 VM and having the same issue of blue screen with "kmode-exception-not-handled" message. The VM is empty. Only Chrome and Virtio drivers installed. The VM start fine but when launch Chrome the VM crash.

I tried your suggestion of host-model flag in xml file but still not working. Same behavior.

Any suggestions?

Thank you

Regards

 

Do you have "kvm.ignore_msrs=1" in your systemlinux config? Its under the flash drive settings?

@david279 Your suggestion seems to have solved the issue. I will deeply test the VM in next days.

Someone know if and when the qemu bug/issue will be fixed?

Thank you

Regards

I'm just building my first unraid server and facing this issue. (I need to use the beta version because in the stable one the NIC driver of my board is not included yet).

So I added "kvm.ignore_msrs=1" to the syslinux.cfg file but through this the VM Manager and the array want startup anymore. Is it possible that someone shares an example of the syslinux file or briefly describes where the command has to be inserted?

Thanks and best regards

I had a similar issue. Windows 10 VM boot-looping with blue screen. Ryzen 3950x. Solved it by adding the following to the end of the VM xml as suggested elswhere on this forum: 

 

  <qemu:commandline>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/>
  </qemu:commandline>

 

@eribob WOW! Tanks. This code before the closing domain part "</domain>" works perfectly. My VMs now starts as expected.

No problem! Someone with more knowledge will have to decipher the meaning of these qemu arguments though... 😃 

Hey I have ryzen 3900x  adding this qemu command line, it seems i can not able this "-amd-stibp" say my cpu doesnt have this feature.

anyway seems works with host-model, but hyperV doesn't work then  I need it to have WSL enabled and windows sandbox.