Bug 1979205 - [virtio-win][viostor] windows guest can not boot with indirect_desc=off
Summary: [virtio-win][viostor] windows guest can not boot with indirect_desc=off
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.5
Hardware: x86_64
OS: Windows
Target Milestone: beta
: ---
Assignee: Vadim Rozenfeld
QA Contact: menli@redhat.com
: 1979830 (view as bug list)
Depends On: 1983901
Blocks: 1979830
TreeView+ depends on / blocked
Reported: 2021-07-05 09:01 UTC by menli@redhat.com
Modified: 2021-11-10 02:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1979830 (view as bug list)
Last Closed: 2021-11-09 18:52:47 UTC
Type: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:4341 0 None None None 2021-11-09 18:53:27 UTC

Description menli@redhat.com 2021-07-05 09:01:54 UTC
Description of problem:
windows guest can not boot with indirect_desc=off

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.boot guest with following command line:
 /usr/libexec/qemu-kvm \
    -name 'bug reproduce' \
    -machine q35 \
    -nodefaults \
    -vga std  \
    -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
    -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
    -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
    -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
    -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
    -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \
    -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \
    -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \
    -blockdev node-name=file_stg1,driver=file,cache.direct=on,cache.no-flush=off,filename=win2016_bios.qcow2,aio=threads \
    -blockdev node-name=drive_stg1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_stg1 \
    -device virtio-blk-pci,id=stg1,drive=drive_stg1,bus=pci.8,addr=0x0,indirect_desc=off   \
    -device virtio-net-pci,mac=9a:36:83:b6:3d:05,id=idJVpmsF,netdev=id23ZUK6,bus=pci.3  \
    -netdev tap,id=id23ZUK6,vhost=on \
    -m 14336  \
    -smp 2,maxcpus=4 \
    -cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,hv_evmcs,hv-vendor-id=KVMtest \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2016/en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso \
    -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
    -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-190.iso \
    -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
    -vnc :1  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -qmp tcp:0:1231,server,nowait \
    -monitor stdio \

Actual results:
Guest can not boot, wait some time guest will BSOD.

Expected results:
Guest can start normally.

Additional info:
1.can also hit it in virtio-win-prewhql-0.1-203.iso, so it is not a regression issue

Comment 1 menli@redhat.com 2021-07-08 01:07:45 UTC
*** Bug 1979830 has been marked as a duplicate of this bug. ***

Comment 7 Vadim Rozenfeld 2021-07-13 05:58:09 UTC
please check with new drivers from build 204

Comment 8 menli@redhat.com 2021-07-13 12:22:37 UTC
Reproduce with virtio-win-prewhql-0.1-190.iso version(steps same as comment#0), result is: guest can not start
Verified with virtio-win-prewhql-0.1-204.iso(steps same as comment#0), result is: guest can start normally
So this issue is fixed, change status to verified.

Comment 11 errata-xmlrpc 2021-11-09 18:52:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.