Blue Screen when installing Windows 10/11.

[vunerta]

There is no problem with windows 7 installation but Windows 10/11 not work for me. I tried LTSB 2016 / W10 22H2/ WIN 11.

Stop code: IRQL NOT LESS OR EQUAL

[78]

Can you post the yaml config you used?
Try to switch between i440fx and q35.

[vunerta]

i440fx and q35 same result with both.

default.yaml

name: Default configuration
base: i440fx.yaml

machine:
  memory: 4G
  vcpu: 4
  # Set vcpu thread priority value [-20, 19]
  # A higher value means a lower priority
  priority: 1
  # Turn on BIOS output and performance measurement
  debug: No
  # Turn on hypervisor to lower CPU usage (Hyper-V is used for Windows)
  hypervisor: Yes

objects:
  - name: cmos
    # gmtime for linux, localtime for windows
    rtc: localtime

  - class: qxl
  - class: spice-agent
  - class: qemu-guest-agent
  - class: usb-tablet

  - class: virtio-network
    backend: uip
    mac: 00:50:00:11:22:33
    map: tcp:0.0.0.0:8022-:22

  - class: ata-cdrom 
    image: /home/vusha/Documents/Windows_10_1903_V1_English_x32.iso
  
  - class: ata-cdrom
    image: /home/vusha/Documents/virtio-win-0.1.229.iso

  - class: ata-disk
    image: /home/vusha/Documents/test_mvisor.qcow2
    snapshot: No
  
  # - class: floppy
  #   image: /data/images/floppy.img

  # - class: virtio-block
  #   image: /data/empty.qcow2
  #   snapshot: No

  # - class: virtio-fs
  #   path: /tmp/fuse
  #   disk_name: mvisor-fs
  #   disk_size: 2G
  #   inode_count: 200

  # - class: vfio-pci
  #   sysfs: /sys/bus/mdev/devices/c2e088ba-954f-11ec-8584-525400666f2b
  #   debug: Yes

  # - class: virtio-vgpu
  #   memory: 1G
  #   staging: No
  #   blob: No
  #   node: /dev/dri/renderD131

i440fx.yaml

name: i440fx-machine

machine:
  memory: 4G
  vcpu: 4
  bios: ../share/bios-256k.bin

objects:
# Use the old name pci-host instead of i440fx-host for compatibility
  - class: i440fx-host

# PCI devices connected to PCI Host.
# The PIIX3 must be put first because it must use PCI slot 1
  - class: piix3
  - class: piix3-ide
  - class: piix3-uhci
  - class: piix4-pm
  - class: ac97

# I/O devices connected to PIIX3
  - class: cmos
  - class: debug-console
  - class: dummy-device
  - class: firmware-config
  - class: kvm-clock
  - class: ps2
  - class: i8257-dma
  - class: i82078-fdc

q35.yaml

name: q35-machine

machine:
  memory: 4G
  vcpu: 4
  bios: ../share/bios-256k.bin

objects:
# Use the old name pci-host instead of q35-host for compatibility
  - class: q35-host

# PCI devices connected to PCI Host
  - class: ich9-hda
  - class: ich9-lpc
  - class: ich9-ahci

# I/O devices connected to ICH9 LPC
  - class: cmos
  - class: debug-console
  - class: dummy-device
  - class: firmware-config
  - class: kvm-clock
  - class: ps2

# codec device connected to ICH9 HDA
  - class: hda-duplex

[nooodles2023]

There is no problem with windows 7 installation but Windows 10/11 not work for me. I tried LTSB 2016 / W10 22H2/ WIN 11.

Stop code: IRQL NOT LESS OR EQUAL

It's a fault triggered by windows kernel driver, did the installation of windows have finished?

I have tested the Windows_10_1903_V1_English_x32.iso, it worked.
My host environment is CentOS8.5 4.18.0-408.el8.x86_64.

[78]

Please provide more information about the BSOD issue, such as the IRQ number, so we can look into the device that caused the problem.

[vunerta]

There is no problem with windows 7 installation but Windows 10/11 not work for me. I tried LTSB 2016 / W10 22H2/ WIN 11.
Stop code: IRQL NOT LESS OR EQUAL

It's a fault triggered by windows kernel driver, did the installation of windows have finished?

I have tested the Windows_10_1903_V1_English_x32.iso, it worked. My host environment is CentOS8.5 4.18.0-408.el8.x86_64.

I get this error on the Windows setup screen before I get to the language options. I use Ubuntu 22.04 LTS with 6.2.0-31-generic.

I managed to install Windows 10 with LTSB versions 2015 & 2016 but I cannot use a mouse and I have no access to the internet. I tried "Windows_10_1903_V1_English_x32.iso " but its not work for me.

Please provide more information about the BSOD issue, such as the IRQ number, so we can look into the device that caused the problem.

[78]

The stop code is not detailed. You should try to remove some device or turn off hypervisor (change Yes to No), and restart the installation again. It needs a lot of work.
I managed to install Windows 11 serveral months ago. I will test the latest Windows 11 later.

To fix the mouse problem, make sure you add the USB tablet device in yaml config file. Check the computer device manager to see if you have the USB device.

The internet is available after you install the Virtio Guest drivers.
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso

I preferred setting base: q35.yaml instead of base: i440fx.yaml for Windows 7/10/11.