windows: I got this error when booting up a windows 11 vm

BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0) BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0) KVM: entry failed, hardware error 0xffffffff EAX=00000000 EBX=ea06f638 ECX=000000b2 EDX=000000b2 ESI=00000000 EDI=0000007a EBP=ea06f5a0 ESP=ea06f578 EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES =0000 00000000 ffffffff 00809300 CS =bd00 7ffbd000 ffffffff 00809300 SS =0000 00000000 ffffffff 00809300 DS =0000 00000000 ffffffff 00809300 FS =0000 00000000 ffffffff 00809300 GS =0000 00000000 ffffffff 00809300 LDT=0000 00000000 00000000 00000000 TR =0040 36cce000 00000067 00008b00 GDT= 36ccffb0 00000057 IDT= 00000000 00000000 CR0=00050032 CR2=6b9e17f8 CR3=0975b000 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=qemu-system-x86_64: hw/core/cpu-sysemu.c:76: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0’ failed. KVM: entry failed, hardware error 0xffffffff ❯ ERROR: Forcefully terminating Windows, reason: 0… ❯ Shutdown completed!

About this issue

Original URL
State: closed
Created 4 months ago
Comments: 15 (4 by maintainers)

Most upvoted comments

@mchughmk @SolarXYZ I added a new flag now which disables a few features. Can you pull the new version (v2.07) and set:
environment:
  BOOT_MODE: "windows_plain"
in your compose file or
-e "BOOT_MODE=windows_plain"
in your run command and see if it changes anything? It disables Secure Boot + TPM + Hyper-V and it might make a difference for you.

Thank you, I’ve been running into the exact same issues as the users above (I have a Windows 11 Notebook with AMD Ryzen 7 6800HS, running docker from within WSL2). The boot_mode option kept the container from crashing as described in this issue.

vssn on Mar 15, 2024

@mchughmk @SolarXYZ I added a new flag now which disables a few features. Can you pull the new version (v2.07) and set:

environment:
  HV: "N"
  BOOT_MODE: "windows_plain"

in your compose file or

-e "KVM=N" -e "BOOT_MODE=windows_plain"

in your run command and see if it changes anything? It disables Secure Boot + TPM + Hyper-V and it might make a difference for you.

kroese on Apr 15, 2024

Hi, addind environment: BOOT_MODE: “windows_plain” solved the problem for me. AMD Ryzen 9 7900X

hristomirster on Apr 18, 2024

I think I figured out my particular issue, in case anyone else runs into it. I was assigning more RAM to the docker container than was available to the WSL VM. The fix is to either assign more RAM to WSL in the .wslconfig or work within the default RAM settings (50% of system or 8GB, whichever is less).

mchughmk on Mar 11, 2024

@HendrikHaase No, that is not true. If you use WSL2 on Windows you will have KVM and it works without issue. You are right that it is Linux based but Docker Desktop for Windows uses WSL2 (which is basicly a Linux environment for Windows).

ok, good i am wrong!

how do we go on, what can we test/try? i can replicate the exact same issue on my 5800x3d, windows11 w/ docker via wsl2

HendrikHaase on Mar 7, 2024