UTM with HVF on Intel causes BSOD in Windows guests (IRQL_NOT_LESS_OR_EQUAL) #2368
Comments
|
Unfortunately, the workaround mentioned is only a temporary fix. Even with a fully installed Windows guest, as soon as certain (as of yet unknown) actions are made in the guest OS, it crashes to BSOD again. For example, in the following screen recording I attempt to install the latest VirtIO Guest Tools in my Windows 10 VM, running with HVF. UTM-HVF-BSOD.mov |
|
@conath can you try this build with updated QEMU? https://github.com/utmapp/UTM/actions/runs/634437375 |
|
A Windows 7 x86 install in a x86_64 q35 machine worked using HVF and that build. Going to try a Windows 10 x64 install next. |
|
Windows 10 20H2 x64 install crashed with a new BSOD QEMU argumentsqemu-system-x86_64 -L /…/qemu -S -qmp tcp:127.0.0.1:4444,server,nowait -vga none -spice port…off -device qxl-vga -cpu host -smp cpus=4,sockets=1,cores=4,threads=1 -machine q35, -accel hvf -accel tcg,tb-size=1024 -global PIIX4_PM.disable_s3=1 -global ICH9-LPC.disable_s3=1 -boot order=d -m 4096 -name "Win 10 x64" -device usb-ehci -device usb-tablet -device usb-mouse -device usb-kbd -device virtio-blk-pci,drive=drive0,bootindex=0 -drive "if=none,media=disk,id=drive0,file=/…/Win 10 x64.utm/Images/disk-0.qcow2,cache=writethrough" -drive if=none,media=cdrom,id=drive1 -nic none -uuid 87E35857-5001-4E66-B2E9-1068E964BBD0 -rtc base=localtime -device ide-drive,drive=drive1 |
|
And booting with AHCI as drive interface (via custom arguments) crashes with |
|
Windows XP install crashes in the text mode part when it loads the HAL. The stop code 0x000000a5 points to an ACPI issue and the first parameter (0x000000011) means "The system cannot enter ACPI mode".
Trying the suggestion at the top of the linked support article, which suggests disabling the ACPI driver by pressing F7 before the drivers load, causes the VM to reboot immediately when it does start loading the drivers. |
|
The 0x000000A5 (0x…11, …) happens with the |
|
During more recent testing with Windows Server 2016 and Windows XP Pro X64 Edition, I have discovered that using the q35 system version 2.9 or earlier gets rid of the BSODs! It seems that the newer q35 systems combined with the Hypervisor causes the issue. Specifically, when installing XP and faced with the stopcode 0x000000A5, switching to q35-2.9 results in successful install (if you have AHCI drivers loaded, otherwise you get stopcode 7B due to inaccessible boot drive). |
|
The same BSOD
|
|
I have made a discovery: the BSOD Update: I can reproduce this reliably now. @osy any ideas why this might be happening or is this qemu/hvf territory? Update 2: it seems like it also crashes if the mouse focused in the VM and not moved for a while. Update 3: it just crashed while I was interacting with it, so no, this mouse movement and focus behavior is purely coincidental. |
|
Yes, same BSOD still occurs as of UTM 2.2.4 running |
|
Same issue here on same config as above comment, but a MacBook Pro instead of Air. Are there any known workarounds? I just needed a Windows VM briefly and thought I might give UTM a shot, but it doesn't appear to work at all. |
|
@mpolden Unfortunately the only known workaround is to disable use of the Hypervisor, which means reducing the speed by at least half:
|
|
Hi! I’ve been running QEMU directly from the CLI without using UTM and have been getting this issue regularly, as well. I narrowed it down to Does UTM default to |
|
That’s interesting. Yes it uses host by default but you can change the cpu type in the settings. |
|
I can confirm that changing from |
|
Reopening since the workaround caused #3249 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Last log seemed to have been incorrect (PatchGuard was triggered independent of the issue). This I believe is more accurate: |
|
So the crash is happening in PatchGuard handling but it's not a |
|
@conath I "fixed" this by removing the |
When running a VM with
-accel hvf, a Windows guest will reproducibly crash with a blue screen errorIRQL_NOT_LESS_OR_EQUAL. This issue duplicates #2303.In the case of a Windows 7 and 8.1 guest, the BSOD is confirmed to occur during the first phase of setup.
In the case of a Windows 10 guest, the BSOD occurs repeatably during the first phase of setup or, if the OS is already installed, at least once after the OOBE.
Configuration
Workaround: before installing Windows in the VM, in UTM Preferences, enable "Force slower emulation even when hypervisor is available". Then start the VM and install Windows (it will take about twice as long as expected). After Windows is installed, shut down the VM and disable "Force slower emulation even when hypervisor is available".
The text was updated successfully, but these errors were encountered: