Bug 1851796

Created attachment 1699070 [details]
install/uninstall logs

Test win1064(version 1909), didn't hit this issue.

Hit similar issue with #comment3 step6 on win10-32/64
Could you check if it is the same bug as this? or it is a new bug?


Steps:

1 boot up a new installed win10-64(2004 version) with all virtio device
2 installed old installer tools(virtio-win-1.9.14-4.el8.iso)
3 check driver installed successfully
4 installled new installer tools(virtio-win-1.9.15-0.el8.iso)

Actual result:

after step 4, the mouse/keyboard/tablet don't work.


Expected results:
All driver updated , and mouse/keyboard/tablet work.

Additional:
If not boot with virtio-input device, it update successfully(not include input).

Version:
Guest:win10-32/win10-64
virtio-win-1.9.14-4.el8.iso
virtio-win-1.9.15-0.el8.iso
kernel-4.18.0-240.10.1.el8_3.x86_64
qemu-kvm-5.1.0-17.module+el8.3.1+9213+7ace09c3.x86_64
seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64

(In reply to Yu Wang from comment #5)
> Hit similar issue with #comment3 step6 on win10-32/64
> Could you check if it is the same bug as this? or it is a new bug?
> 
> 
> Steps:
> 
> 1 boot up a new installed win10-64(2004 version) with all virtio device
> 2 installed old installer tools(virtio-win-1.9.14-4.el8.iso)
> 3 check driver installed successfully
> 4 installled new installer tools(virtio-win-1.9.15-0.el8.iso)
> 
> Actual result:
> 
> after step 4, the mouse/keyboard/tablet don't work.
> 
> 
> Expected results:
> All driver updated , and mouse/keyboard/tablet work.
> 
> Additional:
> If not boot with virtio-input device, it update successfully(not include
> input).
> 
> Version:
> Guest:win10-32/win10-64
> virtio-win-1.9.14-4.el8.iso
> virtio-win-1.9.15-0.el8.iso
> kernel-4.18.0-240.10.1.el8_3.x86_64
> qemu-kvm-5.1.0-17.module+el8.3.1+9213+7ace09c3.x86_64
> seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64

It can be the same issue.
Is there any chance to see the Setup API log files
( https://docs.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-device-installation-log-entries )
for both  #comment3  and  #comment5 cases?

Thanks,
Vadim.

Created attachment 1745476 [details]
setupAPI log

Hit this issue again with virtio-win-1.9.16-2.iso on win10-32/64 guest.

Used versions:
kernel-4.18.0-298.el8.x86_64
qemu-kvm-5.2.0-13.module+el8.4.0+10369+fd280775.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.16-2.el8.iso

Best Regards~
Peixiu

Hi guys,

Can you please confirm that only virtio-input doesn't work properly after re-installation?

Thanks,
Vadim.

@menli 
As you focus on virtio-win installer recently,could you help reply?
Thanks.

(In reply to Vadim Rozenfeld from comment #11)
> Hi guys,
> 
> Can you please confirm that only virtio-input doesn't work properly after
> re-installation?
> 
> Thanks,
> Vadim.

yes, only virtio-input doesn't work properly after re-installation.

Thanks
Menghuan

(In reply to menli from comment #13)
> (In reply to Vadim Rozenfeld from comment #11)
> > Hi guys,
> > 
> > Can you please confirm that only virtio-input doesn't work properly after
> > re-installation?
> > 
> > Thanks,
> > Vadim.
> 
> yes, only virtio-input doesn't work properly after re-installation.
> 
> Thanks
> Menghuan

Hi Menghuan,
Can you please provide the qemu command line?

Thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #14)
> (In reply to menli from comment #13)
> > (In reply to Vadim Rozenfeld from comment #11)
> > > Hi guys,
> > > 
> > > Can you please confirm that only virtio-input doesn't work properly after
> > > re-installation?
> > > 
> > > Thanks,
> > > Vadim.
> > 
> > yes, only virtio-input doesn't work properly after re-installation.
> > 
> > Thanks
> > Menghuan
> 
> Hi Menghuan,
> Can you please provide the qemu command line?
> 
> Thanks,
> Vadim.


qemu command line:

 /usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm3' \
    -machine q35 \
    -nodefaults \
    -vga std  \
    -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 \
    -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x3.0x5 \
    -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x3.0x6 \
    -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x3.0x7 \
    -blockdev node-name=file_stg1,driver=file,cache.direct=on,cache.no-flush=off,filename=/mnt/123/win10-64-virtio-scsi.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.2,addr=0x0,bootindex=1 \
    -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pci.4 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/test/data.qcow2,node-name=data_node \
    -blockdev driver=qcow2,node-name=data_disk,file=data_node \
    -device scsi-hd,drive=data_disk,id=disk1,bus=virtio_scsi_pci1.0,serial=kk \
    -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 4G  \
    -smp 2,maxcpus=4 \
    -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/windows/virtio-win-1.9.16-2.el8.iso \
    -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
    -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
    -vnc :10  \
    -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 \
    -device virtio-serial-pci,id=virtio-serial1,max_ports=31,bus=pci.5  \
    -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait  -device virtserialport,bus=virtio-serial1.0,chardev=channel2,name=org.qemu.guest_agent.0,id=port2 \
    -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,bus=pci.6 \
    -device virtio-balloon-pci,id=balloon0,bus=pci.7 \
    -device pvpanic,id=pvpanic0,ioport=0x0505  \
    -device virtio-keyboard-pci,id=kbd0,serial=virtio-keyboard,bus=pci.8 -device virtio-mouse-pci,id=mouse0,serial=virtio-mouse  -device virtio-tablet-pci,id=tablet0,serial=virtio-tablet  \
    -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
    -numa node,memdev=mem \
    -chardev socket,id=char0,path=/tmp/vhostqemu \
    -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs \
    -blockdev node-name=file_stg2,driver=file,cache.direct=on,cache.no-flush=off,filename=/home/test/data1.qcow2,aio=threads \
    -blockdev node-name=drive_stg2,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_stg2 \
    -device virtio-blk-pci,id=stg2,drive=drive_stg2

Thanks
Menghuan

(In reply to menli from comment #15)
> (In reply to Vadim Rozenfeld from comment #14)
> > (In reply to menli from comment #13)
> > > (In reply to Vadim Rozenfeld from comment #11)
> > > > Hi guys,
> > > > 
> > > > Can you please confirm that only virtio-input doesn't work properly after
> > > > re-installation?
> > > > 
> > > > Thanks,
> > > > Vadim.
> > > 
> > > yes, only virtio-input doesn't work properly after re-installation.
> > > 
> > > Thanks
> > > Menghuan
> > 
> > Hi Menghuan,
> > Can you please provide the qemu command line?
> > 
> > Thanks,
> > Vadim.
> 
> 
> qemu command line:
> 
>  /usr/libexec/qemu-kvm \
>     -name 'avocado-vt-vm3' \
>     -machine q35 \
>     -nodefaults \
>     -vga std  \
>     -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 \
>     -device
> pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x3.0x5 \
>     -device
> pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x3.0x6 \
>     -device
> pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x3.0x7 \
>     -blockdev
> node-name=file_stg1,driver=file,cache.direct=on,cache.no-flush=off,filename=/
> mnt/123/win10-64-virtio-scsi.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.2,addr=0x0,bootindex=1 \
>     -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pci.4 \
>     -blockdev
> driver=file,cache.direct=off,cache.no-flush=on,filename=/home/test/data.
> qcow2,node-name=data_node \
>     -blockdev driver=qcow2,node-name=data_disk,file=data_node \
>     -device
> scsi-hd,drive=data_disk,id=disk1,bus=virtio_scsi_pci1.0,serial=kk \
>     -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 4G  \
>     -smp 2,maxcpus=4 \
>     -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/windows/virtio-win-1.9.16-2.el8.iso \
>     -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
>     -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
>     -vnc :10  \
>     -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 \
>     -device virtio-serial-pci,id=virtio-serial1,max_ports=31,bus=pci.5  \
>     -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait  -device
> virtserialport,bus=virtio-serial1.0,chardev=channel2,name=org.qemu.
> guest_agent.0,id=port2 \
>     -object rng-random,filename=/dev/urandom,id=rng0 -device
> virtio-rng-pci,rng=rng0,bus=pci.6 \
>     -device virtio-balloon-pci,id=balloon0,bus=pci.7 \
>     -device pvpanic,id=pvpanic0,ioport=0x0505  \
>     -device virtio-keyboard-pci,id=kbd0,serial=virtio-keyboard,bus=pci.8
> -device virtio-mouse-pci,id=mouse0,serial=virtio-mouse  -device
> virtio-tablet-pci,id=tablet0,serial=virtio-tablet  \
>     -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
>     -numa node,memdev=mem \
>     -chardev socket,id=char0,path=/tmp/vhostqemu \
>     -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs \
>     -blockdev
> node-name=file_stg2,driver=file,cache.direct=on,cache.no-flush=off,filename=/
> home/test/data1.qcow2,aio=threads \
>     -blockdev
> node-name=drive_stg2,driver=qcow2,cache.direct=on,cache.no-flush=off,
> file=file_stg2 \
>     -device virtio-blk-pci,id=stg2,drive=drive_stg2
> 
> Thanks
> Menghuan


Run the virtiofsd daemon on the host first for the command line with virtiofs device.
e.g: 
#/usr/libexec/virtiofsd --socket-path=/tmp/vhostqemu -o source=/tmp/virtiofs_test -o cache=always

(In reply to menli from comment #16)
> (In reply to menli from comment #15)
> > (In reply to Vadim Rozenfeld from comment #14)
> > > (In reply to menli from comment #13)
> > > > (In reply to Vadim Rozenfeld from comment #11)
> > > > > Hi guys,
> > > > > 
> > > > > Can you please confirm that only virtio-input doesn't work properly after
> > > > > re-installation?
> > > > > 
> > > > > Thanks,
> > > > > Vadim.
> > > > 
> > > > yes, only virtio-input doesn't work properly after re-installation.
> > > > 
> > > > Thanks
> > > > Menghuan
> > > 
> > > Hi Menghuan,
> > > Can you please provide the qemu command line?
> > > 
> > > Thanks,
> > > Vadim.
> > 
> > 
> > qemu command line:
> > 
> >  /usr/libexec/qemu-kvm \
> >     -name 'avocado-vt-vm3' \
> >     -machine q35 \
> >     -nodefaults \
> >     -vga std  \
> >     -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 \
> >     -device
> > pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x3.0x5 \
> >     -device
> > pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x3.0x6 \
> >     -device
> > pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x3.0x7 \
> >     -blockdev
> > node-name=file_stg1,driver=file,cache.direct=on,cache.no-flush=off,filename=/
> > mnt/123/win10-64-virtio-scsi.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.2,addr=0x0,bootindex=1 \
> >     -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pci.4 \
> >     -blockdev
> > driver=file,cache.direct=off,cache.no-flush=on,filename=/home/test/data.
> > qcow2,node-name=data_node \
> >     -blockdev driver=qcow2,node-name=data_disk,file=data_node \
> >     -device
> > scsi-hd,drive=data_disk,id=disk1,bus=virtio_scsi_pci1.0,serial=kk \
> >     -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 4G  \
> >     -smp 2,maxcpus=4 \
> >     -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/windows/virtio-win-1.9.16-2.el8.iso \
> >     -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
> >     -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
> >     -vnc :10  \
> >     -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 \
> >     -device virtio-serial-pci,id=virtio-serial1,max_ports=31,bus=pci.5  \
> >     -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait  -device
> > virtserialport,bus=virtio-serial1.0,chardev=channel2,name=org.qemu.
> > guest_agent.0,id=port2 \
> >     -object rng-random,filename=/dev/urandom,id=rng0 -device
> > virtio-rng-pci,rng=rng0,bus=pci.6 \
> >     -device virtio-balloon-pci,id=balloon0,bus=pci.7 \
> >     -device pvpanic,id=pvpanic0,ioport=0x0505  \
> >     -device virtio-keyboard-pci,id=kbd0,serial=virtio-keyboard,bus=pci.8
> > -device virtio-mouse-pci,id=mouse0,serial=virtio-mouse  -device
> > virtio-tablet-pci,id=tablet0,serial=virtio-tablet  \
> >     -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
> >     -numa node,memdev=mem \
> >     -chardev socket,id=char0,path=/tmp/vhostqemu \
> >     -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs \
> >     -blockdev
> > node-name=file_stg2,driver=file,cache.direct=on,cache.no-flush=off,filename=/
> > home/test/data1.qcow2,aio=threads \
> >     -blockdev
> > node-name=drive_stg2,driver=qcow2,cache.direct=on,cache.no-flush=off,
> > file=file_stg2 \
> >     -device virtio-blk-pci,id=stg2,drive=drive_stg2
> > 
> > Thanks
> > Menghuan
> 
> 
> Run the virtiofsd daemon on the host first for the command line with
> virtiofs device.
> e.g: 
> #/usr/libexec/virtiofsd --socket-path=/tmp/vhostqemu -o
> source=/tmp/virtiofs_test -o cache=always

Hi Menghuan,
Thanks a lot for your detailed response.

Do you know if the same problem can be reproduced on machine
type "pc" rather than "q35" ?

Best,
Vadim.

Hi vadim,

Try to test with win10-64, not reproduced on 'pc' type. virtio-input work properly after re-installation.

 /usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm3' \
    -machine pc-i440fx-rhel7.6.0 \
    -nodefaults \
    -device VGA,bus=pci.0 \
    -blockdev node-name=file_stg0,driver=file,cache.direct=on,cache.no-flush=off,filename=/home/test/win10-64-virtio.qcow2,aio=threads \
    -blockdev node-name=drive_stg0,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_stg0 \
    -device virtio-blk-pci,id=stg0,drive=drive_stg0,bus=pci.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 size=4194304k,slots=240,maxmem=268435456k \
    -smp 2,maxcpus=240,sockets=240,cores=1,threads=1 \
    -cpu 'Skylake-Server' \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/virtio-win-1.9.14-4.el8.iso \
    -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
    -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
    -vnc :10  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -qmp tcp:0:1212,server,nowait \
    -monitor stdio \
    -device virtio-keyboard-pci,id=kbd0,serial=virtio-keyboard,bus=pci.0 -device virtio-mouse-pci,id=mouse0,serial=virtio-mouse  -device virtio-tablet-pci,id=tablet0,serial=virtio-tablet  \

Thanks
Menghuan

(In reply to menli from comment #18)
> Hi vadim,
> 
> Try to test with win10-64, not reproduced on 'pc' type. virtio-input work
> properly after re-installation.
> 
>  /usr/libexec/qemu-kvm \
>     -name 'avocado-vt-vm3' \
>     -machine pc-i440fx-rhel7.6.0 \
>     -nodefaults \
>     -device VGA,bus=pci.0 \
>     -blockdev
> node-name=file_stg0,driver=file,cache.direct=on,cache.no-flush=off,filename=/
> home/test/win10-64-virtio.qcow2,aio=threads \
>     -blockdev
> node-name=drive_stg0,driver=qcow2,cache.direct=on,cache.no-flush=off,
> file=file_stg0 \
>     -device virtio-blk-pci,id=stg0,drive=drive_stg0,bus=pci.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 size=4194304k,slots=240,maxmem=268435456k \
>     -smp 2,maxcpus=240,sockets=240,cores=1,threads=1 \
>     -cpu 'Skylake-Server' \
>     -drive
> id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/
> home/kvm_autotest_root/iso/windows/virtio-win-1.9.14-4.el8.iso \
>     -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
>     -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
>     -vnc :10  \
>     -rtc base=localtime,clock=host,driftfix=slew  \
>     -boot order=cdn,once=c,menu=off,strict=off \
>     -enable-kvm \
>     -qmp tcp:0:1212,server,nowait \
>     -monitor stdio \
>     -device virtio-keyboard-pci,id=kbd0,serial=virtio-keyboard,bus=pci.0
> -device virtio-mouse-pci,id=mouse0,serial=virtio-mouse  -device
> virtio-tablet-pci,id=tablet0,serial=virtio-tablet  \
> 
> Thanks
> Menghuan

Thanks a lot Menghuan.

Seems like another q35 related problem.
Can you please post setup logs from both pc and q35
systems one more time?

Best,
Vadim.

Created attachment 1784390 [details]
q35 setupapi log

Created attachment 1784391 [details]
pc setupapi log

according https://bugzilla.redhat.com/show_bug.cgi?id=1851796#c18 this problem 
seems to ne machine type specific and need more time to be analysed properly.
Moving this bug to 8.6

hit the same issue when run virtio-win-1.9.17-1.el8_4 acceptance test.

version:
qemu-kvm-5.2.0-16.module+el8.4.0+11536+725e25d9.2.x86_64
kernel-4.18.0-305.el8.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.17-1.el8_4.iso

Hit the same issue when run virtio-win-1.9.17-2.el8_4 acceptance test.

Version:
kernel-4.18.0-305.el8.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+11721+c8bbc1be.3.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.17-2.el8_4.iso

Hit the same issue when run virtio-win-1.9.17-3.el8_4 acceptance test.

Version:
kernel-4.18.0-305.el8.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+11721+c8bbc1be.3.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.17-3.el8_4.iso

Hit the same issue when run virtio-win-1.9.17-4.el8_4 acceptance test.

Version:
qemu-kvm-5.2.0-16.module+el8.4.0+11923+e8b883e4.4.x86_64
kernel-modules-4.18.0-305.el8.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.17-4.el8_4

1. 210-Host_RHEL.m8.u4.product_av.qcow2.virtio_blk.up.virtio_net.Guest.Win10.i386.io-github-autotest-qemu.win_virtio_driver_install_by_installer.driver_uninstall.q35
2. 215-Host_RHEL.m8.u4.product_av.qcow2.virtio_blk.up.virtio_net.Guest.Win10.x86_64.io-github-autotest-qemu.win_virtio_driver_install_by_installer.driver_uninstall.q35

hit the same issue when run virtio-win-1.9.15-4.el9 acceptance testing.

version:
kernel-5.14.0-0.rc4.35.el9.x86_64
qemu-kvm-6.0.0-10.el9.x86_64
virtio-win-1.9.15-4.el9
seabios-bin-1.14.0-6.el9.noarch

hit the same issue when run virtio-win-1.9.18-2.el8 acceptance testing 

version:
kernel-4.18.0-338.el8.x86_64
qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.18-2.el8

'VirtIO Serial Driver''VirtIO FS Device These two drivers cannot be uninstalled

hit the same issue when run virtio-win-1.9.19-1.el8 acceptance testing 

version:
kernel-4.18.0-339.el8.x86_64
qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-1.9.19-1.el8

(In reply to ChenNana from comment #31)
> hit the same issue when run virtio-win-1.9.18-2.el8 acceptance testing 
> 
> version:
> kernel-4.18.0-338.el8.x86_64
> qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64
> seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
> virtio-win-1.9.18-2.el8
> 
> 'VirtIO Serial Driver''VirtIO FS Device These two drivers cannot be
> uninstalled

Sorry, the previous judgment was wrong, in fact all devices failed to uninstall

hit the same issue when run virtio-win-1.9.19-5.el9 acceptance testing 

kernel-5.14.0-6.el9.x86_64
qemu-kvm-6.0.0-13.el9_b.5.x86_64
seabios-bin-1.14.0-6.el9.noarch
virtio-win-1.9.19-5.el9

Hi Vadim,
As the ITR is set, could you set DTM, so qe can set ITM accordingly.

Thanks.
Xiaoling

Hello Vadim,
Also this one, thanks.

-------------
On RHEL8.6.0 Code freeze time is 2022-02-28 which DTM is 26, and you set DTM to 25, it's risky for QE to verify within 1 week.
So could you move the date a little bit forward,such as 23.

Thanks,
Xiaoling

(In reply to xiagao from comment #36)
> Hello Vadim,
> Also this one, thanks.
> 
> -------------
> On RHEL8.6.0 Code freeze time is 2022-02-28 which DTM is 26, and you set DTM
> to 25, it's risky for QE to verify within 1 week.
> So could you move the date a little bit forward,such as 23.
> 
> Thanks,
> Xiaoling

Done.
Best,
Vadim.

Win10-21h2 also hit this issue on virtio-win-1.9.26-1.el9_0.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

(In reply to Yu Wang from comment #5)
> Hit similar issue with #comment3 step6 on win10-32/64
> Could you check if it is the same bug as this? or it is a new bug?
> 
> 
> Steps:
> 
> 1 boot up a new installed win10-64(2004 version) with all virtio device
> 2 installed old installer tools(virtio-win-1.9.14-4.el8.iso)
> 3 check driver installed successfully
> 4 installled new installer tools(virtio-win-1.9.15-0.el8.iso)
> 
> Actual result:
> 
> after step 4, the mouse/keyboard/tablet don't work.
> 
> 
> Expected results:
> All driver updated , and mouse/keyboard/tablet work.
> 
> Additional:
> If not boot with virtio-input device, it update successfully(not include
> input).
> 
> Version:
> Guest:win10-32/win10-64
> virtio-win-1.9.14-4.el8.iso
> virtio-win-1.9.15-0.el8.iso
> kernel-4.18.0-240.10.1.el8_3.x86_64
> qemu-kvm-5.1.0-17.module+el8.3.1+9213+7ace09c3.x86_64
> seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64


Hi Vadim, hit the same issue on win10 with virtio-win-1.9.34-0.el9_2.iso.

Additionally, the input driver is not signed. Do we need to open another bug to track it?
e.g.
driverquery /si | find /i "VirtIO Input Driver"
2023-05-29 22:27:09: VirtIO Input Driver Helper     N/A           FALSE    N/A
2023-05-29 22:27:09: VirtIO Input Driver            oem5.inf      TRUE     Red Hat, Inc.

The steps:
> 1 boot up a new installed win10-64(2004 version) with all virtio device
> 2 installed old installer tools(virtio-win-1.9.33-0.el9_2.iso)     
> 3 check driver installed successfully
------> and VirtIO Input Driver Helper was signed.
> 4 installled new installer tools(virtio-win-1.9.34-0.el9_2.iso)
------> VirtIO Input Driver Helper was NOT signed.

Btw, we didn't hit the driver not signed issue when updating installer from 1.9.31 to 1.9.33 .

(In reply to xiagao from comment #52)
> (In reply to Yu Wang from comment #5)
> > Hit similar issue with #comment3 step6 on win10-32/64
> > Could you check if it is the same bug as this? or it is a new bug?
> > 
> > 
> > Steps:
> > 
> > 1 boot up a new installed win10-64(2004 version) with all virtio device
> > 2 installed old installer tools(virtio-win-1.9.14-4.el8.iso)
> > 3 check driver installed successfully
> > 4 installled new installer tools(virtio-win-1.9.15-0.el8.iso)
> > 
> > Actual result:
> > 
> > after step 4, the mouse/keyboard/tablet don't work.
> > 
> > 
> > Expected results:
> > All driver updated , and mouse/keyboard/tablet work.
> > 
> > Additional:
> > If not boot with virtio-input device, it update successfully(not include
> > input).
> > 
> > Version:
> > Guest:win10-32/win10-64
> > virtio-win-1.9.14-4.el8.iso
> > virtio-win-1.9.15-0.el8.iso
> > kernel-4.18.0-240.10.1.el8_3.x86_64
> > qemu-kvm-5.1.0-17.module+el8.3.1+9213+7ace09c3.x86_64
> > seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64
> 
> 
> Hi Vadim, hit the same issue on win10 with virtio-win-1.9.34-0.el9_2.iso.
> 
> Additionally, the input driver is not signed. Do we need to open another bug
> to track it?
> e.g.
> driverquery /si | find /i "VirtIO Input Driver"
> 2023-05-29 22:27:09: VirtIO Input Driver Helper     N/A           FALSE   
> N/A
> 2023-05-29 22:27:09: VirtIO Input Driver            oem5.inf      TRUE    
> Red Hat, Inc.

that's weird.
Is it win11 ? last time we updated vioinput for w11 in October 2022
and the rest is one year or even more old
2k22/amd64/vioinput.inf:DriverVer = 10/30/2021,100.90.104.21400^M
w11/amd64/vioinput.inf:DriverVer = 10/06/2022,100.92.104.22700^M
2k12/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
2k12R2/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
2k12R2/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
2k16/amd64/vioinput.inf:DriverVer = 05/16/2021,100.85.104.19900^M
2k19/amd64/vioinput.inf:DriverVer = 05/16/2021,100.85.104.19900^M
w10/amd64/vioinput.inf:DriverVer = 04/26/2022,100.91.104.21900^M
w10/x86/vioinput.inf:DriverVer = 04/26/2022,100.91.104.21900^M
w8/amd64/vioinput.inf:DriverVer = 12/19/2019,62.81.104.17500^M
w8/x86/vioinput.inf:DriverVer = 12/19/2019,62.81.104.17500^M


 
> 
> The steps:
> > 1 boot up a new installed win10-64(2004 version) with all virtio device
> > 2 installed old installer tools(virtio-win-1.9.33-0.el9_2.iso)     
> > 3 check driver installed successfully
> ------> and VirtIO Input Driver Helper was signed.
> > 4 installled new installer tools(virtio-win-1.9.34-0.el9_2.iso)
> ------> VirtIO Input Driver Helper was NOT signed.
> 
> Btw, we didn't hit the driver not signed issue when updating installer from
> 1.9.31 to 1.9.33 .

(In reply to Vadim Rozenfeld from comment #53)
> (In reply to xiagao from comment #52)
> > (In reply to Yu Wang from comment #5)
> > > Hit similar issue with #comment3 step6 on win10-32/64
> > > Could you check if it is the same bug as this? or it is a new bug?
> > > 
> > > 
> > > Steps:
> > > 
> > > 1 boot up a new installed win10-64(2004 version) with all virtio device
> > > 2 installed old installer tools(virtio-win-1.9.14-4.el8.iso)
> > > 3 check driver installed successfully
> > > 4 installled new installer tools(virtio-win-1.9.15-0.el8.iso)
> > > 
> > > Actual result:
> > > 
> > > after step 4, the mouse/keyboard/tablet don't work.
> > > 
> > > 
> > > Expected results:
> > > All driver updated , and mouse/keyboard/tablet work.
> > > 
> > > Additional:
> > > If not boot with virtio-input device, it update successfully(not include
> > > input).
> > > 
> > > Version:
> > > Guest:win10-32/win10-64
> > > virtio-win-1.9.14-4.el8.iso
> > > virtio-win-1.9.15-0.el8.iso
> > > kernel-4.18.0-240.10.1.el8_3.x86_64
> > > qemu-kvm-5.1.0-17.module+el8.3.1+9213+7ace09c3.x86_64
> > > seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64
> > 
> > 
> > Hi Vadim, hit the same issue on win10 with virtio-win-1.9.34-0.el9_2.iso.
> > 
> > Additionally, the input driver is not signed. Do we need to open another bug
> > to track it?
> > e.g.
> > driverquery /si | find /i "VirtIO Input Driver"
> > 2023-05-29 22:27:09: VirtIO Input Driver Helper     N/A           FALSE   
> > N/A
> > 2023-05-29 22:27:09: VirtIO Input Driver            oem5.inf      TRUE    
> > Red Hat, Inc.
> 
> that's weird.
> Is it win11 ? last time we updated vioinput for w11 in October 2022
> and the rest is one year or even more old
> 2k22/amd64/vioinput.inf:DriverVer = 10/30/2021,100.90.104.21400^M
> w11/amd64/vioinput.inf:DriverVer = 10/06/2022,100.92.104.22700^M
> 2k12/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
> 2k12R2/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
> 2k12R2/amd64/vioinput.inf:DriverVer = 05/16/2021,62.85.104.19900^M
> 2k16/amd64/vioinput.inf:DriverVer = 05/16/2021,100.85.104.19900^M
> 2k19/amd64/vioinput.inf:DriverVer = 05/16/2021,100.85.104.19900^M
> w10/amd64/vioinput.inf:DriverVer = 04/26/2022,100.91.104.21900^M
> w10/x86/vioinput.inf:DriverVer = 04/26/2022,100.91.104.21900^M
> w8/amd64/vioinput.inf:DriverVer = 12/19/2019,62.81.104.17500^M
> w8/x86/vioinput.inf:DriverVer = 12/19/2019,62.81.104.17500^M
> 
No, only win10-32/64 hit this issue.
And it only happened with the following steps. And if we just install drivers by installer, it can get signature, while, if updated drivers by installer, this issue will be triggered.

> 
>  
> > 
> > The steps:
> > > 1 boot up a new installed win10-64(2004 version) with all virtio device
> > > 2 installed old installer tools(virtio-win-1.9.33-0.el9_2.iso)     
> > > 3 check driver installed successfully
> > ------> and VirtIO Input Driver Helper was signed.
> > > 4 installled new installer tools(virtio-win-1.9.34-0.el9_2.iso)
> > ------> VirtIO Input Driver Helper was NOT signed.
> > 
> > Btw, we didn't hit the driver not signed issue when updating installer from
> > 1.9.31 to 1.9.33 .

Hi Xiaoling,

Shall we open a new bz(Jira issue) for the vioinput issue?

(In reply to Qianqian Zhu from comment #55)
> Hi Xiaoling,
> 
> Shall we open a new bz(Jira issue) for the vioinput issue?

Ok, it would be good to track the signature failure issue separately, I will do it.

There is a Jira issue(bug) to track the input signature issue.
https://issues.redhat.com/browse/RHEL-574?filter=12415435

Sorry Vadim, we also need to extend this bug's deadline.
Thank you.