Bug 1711167

Two questions.

Can we try qcow2 file instead of null-co?  And can we try combination null-co with scsi-cd?

In my understanding both cases should work.

Best regards,
Vadim.

(In reply to Vadim Rozenfeld from comment #1)
> Two questions.
> 
> Can we try qcow2 file instead of null-co?  And can we try combination
> null-co with scsi-cd?
> 
> In my understanding both cases should work.
> 
> Best regards,
> Vadim.


1. Also hit BOSD after rescan disks with qcow2 file

    -device pcie-root-port,id=pcie.0-root-port-9,slot=9,chassis=9,addr=0x9,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pcie.0-root-port-9,addr=0x0 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/nfs_test/data.qcow2,node-name=data_disk \
    -blockdev driver=qcow2,node-name=disk1,file=data_disk \
    -device scsi-hd,drive=disk1,bus=virtio_scsi_pci1.0,id=data_disk \

Memory dump file: http://fileshare.englab.nay.redhat.com/pub/section2/images_backup/bug1711167/


2. combination null-co with scsi-cd, also hit this issue.

    -device pcie-root-port,id=pcie.0-root-port-9,slot=9,chassis=9,addr=0x9,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pcie.0-root-port-9,addr=0x0 \
    -blockdev node-name=file_none,driver=null-co,read-only=on \
    -blockdev node-name=drive_none,driver=raw,file=file_none,read-only=on \
    -device scsi-cd,id=none,drive=drive_none \

*** Bug 1783214 has been marked as a duplicate of this bug. ***

Hit this issue when unplug balloon device in win2019 guest on rhel8.2.0-av host.
And could reproduce with "blockdev" mode, but won't reproduce with drive mode. Thanks.

hit the same problem as comment 3 when hotplug virtio-blk-pci device to win2019 guest.

host version:
kernel-4.18.0-147.4.1.el8_1.x86_64
qemu-kvm-4.1.0-21.module+el8.1.1+5388+fd51bfbc.x86_64
seabios-1.12.0-5.module+el8.1.1+5309+6d656f05.x86_64
virtio-win-1.9.10-3.el8.noarch
guest:Win2019 (pc + seabios)

hit the same problem as comment 1  on win2012R2 guest.

host version:
kernel-4.18.0-167.el8.x86_64
qemu-kvm-4.2.0-5.module+el8.2.0+5389+367d9739.x86_64
seabios-1.12.0-5.module+el8.2.0+4793+b09dd2fb.x86_64

guest:Win2012R2 (q35 + seabios)

It is easy to hit this issue ，please help to have a look asap ,much thanks.

yes,also reproduce on pc machine(win2012R2 guest)

host version:
kernel-4.18.0-167.el8.x86_64
qemu-kvm-4.2.0-5.module+el8.2.0+5389+367d9739.x86_64
seabios-1.12.0-5.module+el8.2.0+4793+b09dd2fb.x86_64

CML:
 
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm3' \
    -machine pc \
    -nodefaults \
    -device VGA,bus=pci.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0  \
    -blockdev node-name=file_image1,driver=file,cache.direct=on,cache.no-flush=off,filename=os.qcow2,aio=threads \
    -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
    -device scsi-hd,id=image1,drive=drive_image1,bus=virtio_scsi_pci0.0 \
    -device virtio-net-pci,mac=9a:36:83:b6:3d:05,id=idJVpmsF,netdev=id23ZUK6,bus=pci.0  \
    -netdev tap,id=id23ZUK6,vhost=on \
    -m 14336  \
    -smp 2,maxcpus=4 \
    -cpu 'Skylake-Server' \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2012R2/en_windows_server_2012_r2_with_update_x64_dvd_6052708.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-176.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 \

(In reply to menli from comment #9)
> yes,also reproduce on pc machine(win2012R2 guest)
> 
> host version:
> kernel-4.18.0-167.el8.x86_64
> qemu-kvm-4.2.0-5.module+el8.2.0+5389+367d9739.x86_64
> seabios-1.12.0-5.module+el8.2.0+4793+b09dd2fb.x86_64
> 
> CML:
>  
> /usr/libexec/qemu-kvm \
>     -name 'avocado-vt-vm3' \
>     -machine pc \
>     -nodefaults \
>     -device VGA,bus=pci.0 \
>     -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0  \
>     -blockdev
> node-name=file_image1,driver=file,cache.direct=on,cache.no-flush=off,
> filename=os.qcow2,aio=threads \
>     -blockdev
> node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,
> file=file_image1 \
>     -device scsi-hd,id=image1,drive=drive_image1,bus=virtio_scsi_pci0.0 \
>     -device
> virtio-net-pci,mac=9a:36:83:b6:3d:05,id=idJVpmsF,netdev=id23ZUK6,bus=pci.0  \
>     -netdev tap,id=id23ZUK6,vhost=on \
>     -m 14336  \
>     -smp 2,maxcpus=4 \
>     -cpu 'Skylake-Server' \
>     -drive
> id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/
> home/kvm_autotest_root/iso/ISO/Win2012R2/
> en_windows_server_2012_r2_with_update_x64_dvd_6052708.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-176.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 \

Great. 
Can you post crash dump from pc type VM as well.
Thank you,
Vadim.

post crash dump to following link, please access to bz1711167 to download it,thanks.

http://fileshare.englab.nay.redhat.com/pub/section2/coredump/

(In reply to menli from comment #11)
> post crash dump to following link, please access to bz1711167 to download
> it,thanks.
> 
> http://fileshare.englab.nay.redhat.com/pub/section2/coredump/bz1711167/

I also hit this issue after hotplug/unplug balloon device on win8-32 guest with pc machine type, there is an auto rescan operation in device manager after hotplug/unplug.

QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

When I test block_resize and rescan in disk management, found if use virtio-scsi device, bsod will happen, but if use virtio-block, it will not happen BSOD. 
@qingwang, could you confirm if this situation is true?

Hi Vadim,

On new virtio-win-prewhql-181 version, tested with virtio_blk disk, reproduced this issue when do rescan operation,
but on virtio-win-prewhql-180 version, tested with virtio_blk disk, cannot reproduce issue when do rescan operation.

Tested cli for upper both tests(only attach 1 virtio_blk system disk):

-blockdev node-name=file_image1,driver=file,aio=threads,filename=/home/kvm_autotest_root/images/win10-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,serial=TARGET_DISK0,bus=pci.0,addr=0x4 \

As above test results, there have a regression issue on virtio-win-prewhql-181, if we need to file a new bug for viostor?

And, on version virtio-win-prewhql-181, I also tested without serial=TARGET_DISK0 on virtio-blk-pci(-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pci.0,addr=0x4), cannot reproduce this issue.


Thanks a lot~
Peixiu

(In reply to Peixiu Hou from comment #18)
> Hi Vadim,
> 
> On new virtio-win-prewhql-181 version, tested with virtio_blk disk,
> reproduced this issue when do rescan operation,
> but on virtio-win-prewhql-180 version, tested with virtio_blk disk, cannot
> reproduce issue when do rescan operation.
> 
> Tested cli for upper both tests(only attach 1 virtio_blk system disk):
> 
> -blockdev
> node-name=file_image1,driver=file,aio=threads,filename=/home/
> kvm_autotest_root/images/win10-64-virtio.qcow2,cache.direct=on,cache.no-
> flush=off \
> -blockdev
> node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,
> file=file_image1 \
> -device
> virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,
> serial=TARGET_DISK0,bus=pci.0,addr=0x4 \
> 
> As above test results, there have a regression issue on
> virtio-win-prewhql-181, if we need to file a new bug for viostor?
> 
> And, on version virtio-win-prewhql-181, I also tested without
> serial=TARGET_DISK0 on virtio-blk-pci(-device
> virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,
> bus=pci.0,addr=0x4), cannot reproduce this issue.
> 
> 
> Thanks a lot~
> Peixiu

Yws, since it is a regression, please open a new bug assigned to me.

Best,
Vadim.

(In reply to Vadim Rozenfeld from comment #19)
> (In reply to Peixiu Hou from comment #18)
> > Hi Vadim,
> > 
> > On new virtio-win-prewhql-181 version, tested with virtio_blk disk,
> > reproduced this issue when do rescan operation,
> > but on virtio-win-prewhql-180 version, tested with virtio_blk disk, cannot
> > reproduce issue when do rescan operation.
> > 
> > Tested cli for upper both tests(only attach 1 virtio_blk system disk):
> > 
> > -blockdev
> > node-name=file_image1,driver=file,aio=threads,filename=/home/
> > kvm_autotest_root/images/win10-64-virtio.qcow2,cache.direct=on,cache.no-
> > flush=off \
> > -blockdev
> > node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,
> > file=file_image1 \
> > -device
> > virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,
> > serial=TARGET_DISK0,bus=pci.0,addr=0x4 \
> > 
> > As above test results, there have a regression issue on
> > virtio-win-prewhql-181, if we need to file a new bug for viostor?
> > 
> > And, on version virtio-win-prewhql-181, I also tested without
> > serial=TARGET_DISK0 on virtio-blk-pci(-device
> > virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,
> > bus=pci.0,addr=0x4), cannot reproduce this issue.
> > 
> > 
> > Thanks a lot~
> > Peixiu
> 
> Yws, since it is a regression, please open a new bug assigned to me.
> 

Thanks, filed a new bug https://bugzilla.redhat.com/show_bug.cgi?id=1828658, and has assigned to you~

Best Regards~
Peixiu

> Best,
> Vadim.

Hit same issue on 8.2.1-av with win2019 guest after hotplug balloon device under pc machine type.

Please update drivers to the latest build 203 available at
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28400644

and give it another try.

Thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #22)
> Please update drivers to the latest build 203 available at
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28400644

The link is not available now, would you please provide another one?

> 
> and give it another try.
> 
> Thanks,
> Vadim.

(In reply to Yumei Huang from comment #23)
> (In reply to Vadim Rozenfeld from comment #22)
> > Please update drivers to the latest build 203 available at
> > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28400644
> 
> The link is not available now, would you please provide another one?

latest 184 build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1191255

Needinfo menli as well she hit similar issue with rng device.

Tested on :
4.18.0-193.2.1.el8_2.x86_64
qemu-kvm-core-4.2.0-21.module+el8.2.1+6586+8b7713b9.x86_64
virtio-win-prewhql-0.1-184

Test steps:

1.create image
qemu-img create -f qcow2 /home/kvm_autotest_root/images/stg1.qcow2 1G

2.Boot vm
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1' \
    -machine q35  \
    -nodefaults \
    -device VGA,bus=pcie.0,addr=0x1  \
    -device pvpanic,ioport=0x505,id=idZcGD6F  \
    -device pcie-root-port,id=pcie.0-root-port-2,slot=2,chassis=2,addr=0x2,bus=pcie.0 \
    -device qemu-xhci,id=usb1,bus=pcie.0-root-port-2,addr=0x0 \
    -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \
    -device virtio-scsi-pci,id=scsi0,bus=pcie.0-root-port-4,addr=0x0 \
    \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/images/win2019-64-virtio-scsi.qcow2,node-name=host_disk2 \
    -blockdev driver=qcow2,node-name=disk_2,file=host_disk2 \
    -device scsi-hd,drive=disk_2,bus=scsi0.0,id=host_disk_2 \
    \
    -blockdev node-name=data_image1,driver=file,cache.direct=on,cache.no-flush=off,filename=/home/kvm_autotest_root/images/stg1.qcow2,aio=threads \
    -blockdev node-name=data1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=data_image1 \
    -device scsi-hd,id=disk1,drive=data1,bus=scsi0.0 \
    -device pcie-root-port,id=pcie.0-root-port-5,slot=5,chassis=5,addr=0x5,bus=pcie.0 \
    -device virtio-net-pci,mac=9a:55:56:57:58:59,id=id18Xcuo,netdev=idGRsMas,bus=pcie.0-root-port-5,addr=0x0  \
    -netdev tap,id=idGRsMas,vhost=on \
    -m 13312  \
    -smp 24,maxcpus=24,cores=12,threads=1,sockets=2  \
    -cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2019/en_windows_server_2019_updated_march_2019_x64_dvd_2ae967ab.iso \
    -device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,bus=ide.0,unit=0 \
    -drive id=drive_virtio,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-176.iso \
    -device ide-cd,id=virtio,drive=drive_virtio,bootindex=3,bus=ide.1,unit=0 \
    -drive id=drive_winutils,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/winutils.iso \
    -device ide-cd,id=winutils,drive=drive_winutils,bus=ide.2,unit=0\
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -vnc :5  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -device pcie-root-port,id=pcie_extra_root_port_0,slot=6,chassis=6,addr=0x6,bus=pcie.0 \
    -monitor stdio \
    -qmp tcp:0:5955,server,nowait \

3,select the disk online it in diskmanager then rescan disk


4.houtunplug disk then rescan disk in diskmanager

{'execute':'qmp_capabilities'}

{"execute":"device_del","arguments":{"id":"disk1"}}


5.hotplug back then 

{'execute':'device_add','arguments':{'driver':'scsi-hd','id':'disk1','drive':'data1','bus':'scsi0.0'}}

Not hit BSOD issue

Test with virtio-win-prewhql-0.1-184 for hotplug rng device with blockdev+scsi,not hit BSOD issue.

change component to virtio-win according to comment#25 and comment#26.

(In reply to lijin from comment #24)
> (In reply to Yumei Huang from comment #23)
> > (In reply to Vadim Rozenfeld from comment #22)
> > > Please update drivers to the latest build 203 available at
> > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28400644
> > 
> > The link is not available now, would you please provide another one?
> 
> latest 184 build:
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1191255

Thanks, the issue is gone with this build.

> 
> Needinfo menli as well she hit similar issue with rng device.

Change status to verified

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, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2020:3055