Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-44581

Guest power off failed with iommu_platform=on and enable iothread [rhel-10.beta]

    • None
    • Moderate
    • rhel-sst-virtualization-storage
    • ssg_virtualization
    • 8
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • x86_64
    • Windows
    • None

      (Clone from RHEL-30894 Guest power off failed with the virtio-blk-pci,...,iommu_platform=on

      same issue on 

      Red Hat Enterprise Linux release 10.0 Beta (Coughlan)
      6.9.0-0.rc2.1.el10.x86_64
      qemu-kvm-9.0.0-2.el10.x86_64

       

      )

      What were you trying to do that didn't work?
      WS2025 guest cannot be booted up with the iommu enabled

      iommu related commands:

      -machine q35,kernel-irqchip=split,pflash0=drive_ovmf_code,pflash1=drive_ovmf_vars \
      -device intel-iommu,intremap=on,device-iotlb=on,caching-mode=off,eim=on \

      -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:52:0d:19:1f:69,mq=on,bus=pci.2,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on -netdev tap,script=/etc/qemu-ifup1,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:7f:7c:0e:6a,mq=on,bus=pci.3,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on \
      -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=SUTINT9402502,node-name=system_file -blockdev driver=qcow2,node-name=drive_system_disk,file=system_file -object iothread,id=thread0 -device virtio-blk-pci,scsi=off,iothread=thread0,drive=drive_system_disk,id=virtio-disk0,bootindex=1,bus=pci.4,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on \

      Please provide the package NVR for which bug is seen:
      5.14.0-428.el9.x86_64
      qemu-kvm-8.2.0-11.el9_4.x86_64
      virtio-win-latest-signed-el9.iso
      edk2-ovmf-20231122-6.el9.noarch

      How reproducible:
      100%

      Steps to reproduce
      1.Boot the win2025 vm up with the iommu device
      /usr/libexec/qemu-kvm -name SUTINT9402564 -cpu Broadwell-noTSX,vmx=on,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0xfff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,hv-vendor-id=KVMtest \
      -enable-kvm -nodefaults \
      -m 8G -smp 6,cores=6 \
      -k en-us -boot menu=on \
      -uuid 65d4d34b-dc6f-4a52-b9f9-8a3fce3af235 \
      -device piix3-usb-uhci,id=usb -device usb-tablet,id=tablet0 \
      -chardev socket,id=charmonitor,path=/tmp/SUTINT9402564,server=on,wait=off \
      -mon chardev=charmonitor,id=monitor,mode=control \
      -rtc base=localtime,clock=host,driftfix=slew \
      -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x3 \
      -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x3.0x1 \
      -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x3.0x2 \
      -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x3.0x3 \
      -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x3.0x4 \
      -netdev tap,script=/etc/qemu-ifup,id=hostnet0,vhost=on \
      -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:52:0d:19:1f:69,mq=on,bus=pci.2,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on -netdev tap,script=/etc/qemu-ifup1,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:7f:7c:0e:6a,mq=on,bus=pci.3,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on \
      -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=SUTINT9402502,node-name=system_file -blockdev driver=qcow2,node-name=drive_system_disk,file=system_file -object iothread,id=thread0 -device virtio-blk-pci,scsi=off,iothread=thread0,drive=drive_system_disk,id=virtio-disk0,bootindex=1,bus=pci.4,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on \
      -device usb-ehci,id=ehci0,bus=pci.5 -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2022/en-us_windows_server_2022_updated_july_2023_x64_dvd_541692c3.iso -device ide-cd,id=cd1,drive=drive_cd1,bus=ide.0,unit=0 \
      -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-latest-signed-el9.iso \
      -vnc :0 -vga std -monitor stdio \
      -blockdev node-name=file_ovmf_code,driver=file,filename=SUTINT9402564_ovmf/OVMF_CODE.secboot.fd,auto-read-only=on,discard=unmap -blockdev node-name=drive_ovmf_code,driver=raw,read-only=on,file=file_ovmf_code \
      -blockdev node-name=file_ovmf_vars,driver=file,filename=SUTINT9402564_ovmf/OVMF_VARS.fd,auto-read-only=on,discard=unmap -blockdev node-name=drive_ovmf_vars,driver=raw,read-only=off,file=file_ovmf_vars \
      -machine q35,kernel-irqchip=split,pflash0=drive_ovmf_code,pflash1=drive_ovmf_vars \
      -device intel-iommu,intremap=on,device-iotlb=on,caching-mode=off,eim=on \
      -drive file=usb-disk-wxI.raw,if=none,id=drive-usb-2-0,media=disk,format=raw,cache=none,werror=stop,rerror=stop,aio=threads -device usb-storage,bus=ehci0.0,drive=drive-usb-2-0,id=usb-2-0,removable=on

      2. Check the vm screen --> always trying boot into the os, but cannot.
      3.

      Expected results
      Boot into os sucess

      Actual results
      Win2025 guest Cannot boot into os

              kwolf@redhat.com Kevin Wolf
              qingwangrh qing wang
              virt-maint virt-maint
              qing wang qing wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: