FS#67620 - KVM in Linux 5.8.1 causes Windows VM to bluescreen on boot using QEMU
Attached to Project:
Arch Linux
Opened by kk (Ampera) - Monday, 17 August 2020, 17:16 GMT
Last edited by freswa (frederik) - Monday, 17 August 2020, 22:46 GMT
Opened by kk (Ampera) - Monday, 17 August 2020, 17:16 GMT
Last edited by freswa (frederik) - Monday, 17 August 2020, 22:46 GMT
|
Details
Description:
Updating to linux 5.8.1.arch1-1 has caused a Windows VM being operated through libvirt/QEMU to bluescreen on start (see screenshot) VM is known good and booting, using linux-lts 5.4.58-1 allows VM to boot properly. This issue is new as of 5.8, 5.7 did not have this issue for me. Quick google search failed to find any mention upstream, or anywhere else. I did find mention of a similar issue to do with Zen 2 and a speculative execution bug of some sort relating specifically to Zen 2 chips (which I am using). Additional info: CPU: Ryzen 9 3950X Motherboard: GIGABYTE X570 AORUS ELITE WIFI libvirt version: libvirt 6.5.0-1 QEMU version: qemu 5.1.0-1 virt-manager version: virt-manager 2.2.1-2 Windows 10 Version: Pro 2004, Build 19041.450 Steps to reproduce: AMD Zen 2 CPU may be required to reproduce this bug Prepare a Windows 10 VM using QEMU/KVM using libvirt and virt-manager, 8 vCPUs (4 cores, SMT2 configured topology), 16GB RAM, virtio storage and network, Q35, OVMF EFI Install and boot linux 5.8.1.arch1-1 (if not already) and boot the Windows 10 VM, a BSoD will occur with stop code "KERNEL SECURITY CHECK FAILURE" (see screenshot) Install and boot linux-lts 5.4.58-1 and boot the Windows 10 VM, it will boot up without problem. |
This task depends upon
Closed by freswa (frederik)
Monday, 17 August 2020, 22:46 GMT
Reason for closing: Upstream
Additional comments about closing: I can't reproduce this on my Zen system. Please report this upstream to get this sorted out. Feel free to fill a re-open request if we need to include certain patches. Thank you
Monday, 17 August 2020, 22:46 GMT
Reason for closing: Upstream
Additional comments about closing: I can't reproduce this on my Zen system. Please report this upstream to get this sorted out. Feel free to fill a re-open request if we need to include certain patches. Thank you