Created attachment 1480044 [details]
network-driver-2

Created attachment 1480045 [details]
network-driver-3

Do we believe this is specifically a regression in
virtio-win-1.9.6-1.el7.noarch?

Do we have the virt-v2v log of the conversion? (in case it contains
anything interesting - but I suspect it will not)

Created attachment 1480049 [details]
virt-v2v-win7-network-driver.log

After confirm with the reporter, it can be reproduced with virtio-win-prewhql-160, so change the component.

Yan,

This bug looks quite similar to bz1411596. 
Could you have a look at this issue?

Thanks.

Provide qemu info for lijin as below:

# ps aux |grep qemu
qemu      1009 13.7  3.3 1976684 1102012 ?     Sl   17:23   1:41 /usr/libexec/qemu-kvm -name guest=esx6.5-win2008r2-x86_64,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-48-esx6.5-win2008r2-x86/master-key.aes -machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8bf2821e-826a-4016-a9fb-e4b924d0473f -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=30,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/esx6.5-win2008r2-x86_64-sda,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=33 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:50:56:a2:a3:89,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:1 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -device pvpanic,ioport=1285 -msg timestamp=on

I think it relates to the fact that now MS is issuing only SHA2 certificates and the images might not be updated to the latest security updates.

For info here:
https://docs.microsoft.com/en-us/security-updates/securityadvisories/2014/2949927 , 

Brief explanation:
1. Drivers for Win7 and Windows 2008R2 were signed with SHA1 signature. And those versions of Windows couldn't correctly parse SHA2 signatures.

2. MS decided that SHA1 is no longer secured and rolled out security updates. From this point drivers could be either SHA1 or SHA2 signed.

3. At some point, MS stopped issuing completely SHA1 certificates (https://support.microsoft.com/en-us/help/3123479/microsoft-security-advisory-deprecation-of-sha-1-hashing-algorithm-for)

4. Attaching signature details for Win7 x64 NetKVM driver

So the solution is to update the images to include SHA2 support.

Does this mean we'll no longer be able to support Windows 7 & 2008R2?
Or did they issue updates to those versions of Windows to allow them
to support SHA2 certs?

In any case this will require some virt-v2v docs changes ...

Updates are downloadable from https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929

Test the bug with latest virt-v2v according to comment11
virt-v2v-1.38.2-12.el7.x86_64
libguestfs-1.38.2-12.el7.x86_64
virtio-win-1.9.6-1.el7.noarch


Steps:
1.Update win7 sp1 x64 guest with Windows6.1-KB3033929-x64.msu on ESXi6.7 host and convert the guest to rhv by virt-v2v after updating

#virt-v2v -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-win7-x86_64 -n default --password-file /tmp/passwd -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /tmp/rhvpasswd -oo rhv-cafile=/home/ca.pem  -oo rhv-direct -of raw  -b ovirtmgmt  -on win7-update-network  -v -x |& tee > virt-v2v-win7-update-network.log

2.After conversion,power on guest on rhv and check network device can be installed virtio driver automatically and digital signer is  Microsoft Windows

Created attachment 1482627 [details]
win7-sp1-x86

The win7sp1-x86 guest of comment14 has no problem to install virtio for network after virt-v2v conversion if the original guest has been activated by product key.

So if want to install virtio driver for network in win7sp1 and win2008r2 guest automatically after virt-v2v conversion, the following two conditions must be satisfied in original guest.

(1)Win7 sp1 x64/x86 and win2008r2 guests must has been activated by product key
(2)Win7 sp1 x64/x86 and win2008r2 guests must be updated with Windows6.1-KB3033929-x86/64.msu

I think the bug could be closed now

Closing this per comment 17.

Also closing bug 1624321 which is a clone of this bug for RHEL 8.

Note that a documentation change is required to virt-v2v.  That
is filed separately as bug 1624878.

Created attachment 1583050 [details]
Load driver faile due to error "No signed device drivers were found"

Hi Yan,

I hit a issue seems related this one, could you help to confirm if it's a new issue? thanks~

Cannot install netkvm driver during install win7-64 guest os. on Installing windows page, Load netkvm Driver from virtio-win-1.9.8/NetKvm/w7/amd64/, will report error "No signed device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK". detail please refer to attachment No_signed.pnp picture.

Also tried follows testing:
1. Tried with virtio-win-1.9.8-0, reproduced this issue.
2. Tried with virtio-win-1.9.8-2, reproduced this issue.
3. Tried with virtio-win-1.9.7-3, reproduced this issue.
4. Tried with vitio-win-1.9.6-1, reproduced this issue.
5. It can be reproduced on host rhel8.0.0, rhel8.0.1, rhel8.1.0, rehl7.6.z.
6. Only hit this issue with netkvm driver, cannot reproduced this issue with all other virtio-win drivers(vioscsi, viostor, balloon, viorng, vioserial, pvpanic).
7. Tried test with win7-32 guest, cannot reproduced this issue, the netkvm driver can be loaded successfully during guest os installing.

Booted command line:
================================================================================================================================================
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1' \
    -machine q35  \
    -nodefaults \
    -device VGA,bus=pcie.0,addr=0x1  \
    -device pvpanic,ioport=0x505,id=id4Fppe5  \
    -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-3,addr=0x0 \
    -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=win7-64-4.qcow2 \
    -device scsi-hd,id=image1,drive=drive_image1 \
    -device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \
    -object iothread,id=thread0 \
    -drive id=drive_disk1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=storage-4.qcow2 \
    -device virtio-blk-pci,id=disk1,drive=drive_disk1,iothread=thread0,bus=pcie.0-root-port-4,addr=0x0 \
    -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:da:db:dc:dd:de,id=idbe91aZ,vectors=4,netdev=idUUNwTj,bus=pcie.0-root-port-5,addr=0x0  \
    -netdev tap,id=idUUNwTj,vhost=on \
    -device e1000,mac=9a:da:db:dc:12:2a,id=idbe34aZ,netdev=idUUssTj \
    -netdev tap,id=idUUssTj,vhost=on \
    -m 7168  \
    -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=/usr/share/virtio-win/virtio-win.iso\
    -device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,bus=ide.0,unit=0 \
    -vnc :6  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -monitor stdio \
    -qmp tcp:0:4448,server,nowait \
    -cdrom /home/kvm_autotest_root/iso/ISO/Windows7/en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso \
==================================================================================================================================================

Thanks a lot~
Peixiu

And I also hit Windows Security warning(Windows can't verify the publisher of this driver software) when install netkvm driver after the guest installation, tried updated the Windows6.1-KB3033929-x86/64.msu, it can be resolved. 
It's weird that only netkvm will hit this issue and comment#20 one, all other drivers not hit them.

Thanks~
Peixiu

Adding Yuri as well.

I've just installed a new Windows Server 2008 R2 guest, from:

  en_windows_server_2008_r2_with_sp1_x64_dvd_617601

I can't install the NetKVM driver in it, from:

  /usr/share/virtio-win/virtio-win-1.9.6.iso

(package "virtio-win-1.9.6-1.el7.noarch").

Because the guest has no network connectivity, I cannot use Windows Update.

I've considered formatting a new virtual disk image for the guest (attaching it as an extra drive), populated with a file (any file, really) that I could hopefully download from:

  https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929

The article itself states, "The updates are also available via the download links in the Affected Software table in this advisory".

Except, if I click the following link in that table:

  Windows Server 2008 R2 for x64-based Systems Service Pack 1 (3033929)(1)
  https://www.microsoft.com/downloads/details.aspx?familyid=1f919b1e-ef1d-4c7d-b478-cb219fda4e82

I get:

  404 - File or directory not found.
  The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Googling "Windows6.1-KB3033929-x64.msu" led me to:

  https://www.microsoft.com/en-us/download/details.aspx?id=46148
  -> "Windows6.1-KB3033929-x64.msu"
  -> sha256: 5318587007edb6c8b29310ff18da479a162b486b9101a7de735f94a70dbc3b31

and documentation (naming the above sha256sum too) at

  https://support.microsoft.com/en-us/help/3033929/microsoft-security-advisory-availability-of-sha-2-code-signing-support

I'd suggest two actions:

(1) updating the v2v documentation originally added for bug 1624878
(2) advertizing (not sure where) the latest such virtio-win build that does *not* require sha256 compat from the Windows 7 OS family.

(Comment 0 here says, "virtio-win-1.9.4-2.el7.noarch" does not reproduce the problem -- so maybe I'll just downgrade virtio-win to that version, for installing NetKVM, rather than formatting an extra disk image with "Windows6.1-KB3033929-x64.msu".)

Thanks
Laszlo

(In reply to Laszlo Ersek from comment #24)
> I've just installed a new Windows Server 2008 R2 guest, from:
> 
>   en_windows_server_2008_r2_with_sp1_x64_dvd_617601
> 
> I can't install the NetKVM driver in it, from:
> 
>   /usr/share/virtio-win/virtio-win-1.9.6.iso
> 
What was the exact problem installing netkvm driver?
Was it the warning "Windows can't verify the publisher of this driver software" or something different?
This does not disallow the driver installation, correct?

Hi Yuri,

(In reply to ybendito from comment #25)
> (In reply to Laszlo Ersek from comment #24)
> > I've just installed a new Windows Server 2008 R2 guest, from:
> > 
> >   en_windows_server_2008_r2_with_sp1_x64_dvd_617601
> > 
> > I can't install the NetKVM driver in it, from:
> > 
> >   /usr/share/virtio-win/virtio-win-1.9.6.iso
> > 
> What was the exact problem installing netkvm driver?
> Was it the warning "Windows can't verify the publisher of this driver
> software"

Yes, that was the problem. Windows displayed that error message in a popup with a large red banner.

> or something different?
> This does not disallow the driver installation, correct?

That's correct, I could have overridden the warning, but I chose not to.

Ultimately, I downloaded "Windows6.1-KB3033929-x64.msu", from the location I noted in comment 24, to my virt host. I formatted a new ISO image with that file. Then I temporarily swapped this ISO image with the virtio-win.iso image in the domain's CD-ROM drive (using "virsh change-media"). So I didn't even have to power down the domain. Once the MSU was installed, I swapped the virtio-win.iso back, and then the NetKVM installation compelted fine.

Thanks!

Hi vadim,

I hit a issue seems related this one, could you help to confirm if it's the same  issue? thanks~

Cannot install viostor driver during install win2008R2  guest os. on Installing windows page, Load viostor Driver from virtio-win-1.9.10 /viostor/2k8R2/amd64/, will report error "No signed device drivers were found.

Also tried follows testing:

Tried with virtio-win-1.9.9-3, not reproduce this issue.
I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is 171, both 171 and 172 work fine. Only rpm package can reproduce this issue even though the version is the same.




Thanks a lot~

Menghuan

(In reply to menli from comment #28)
> Hi vadim,
> 
> I hit a issue seems related this one, could you help to confirm if it's the
> same  issue? thanks~
> 
> Cannot install viostor driver during install win2008R2  guest os. on
> Installing windows page, Load viostor Driver from virtio-win-1.9.10
> /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> found.
> 
> Also tried follows testing:
> 
> Tried with virtio-win-1.9.9-3, not reproduce this issue.
> I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> even though the version is the same.
> 
> 
> 
> 
> Thanks a lot~
> 
> Menghuan

Hi Menghuan,
Where did you get that virtio-win-1.9.10 from.
FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
building process. We decided to do it mostly because we don't have a valid
SHA-1 certificate any Longer.

Best,
Vadim.

(In reply to Vadim Rozenfeld from comment #29)
> (In reply to menli from comment #28)
> > Hi vadim,
> > 
> > I hit a issue seems related this one, could you help to confirm if it's the
> > same  issue? thanks~
> > 
> > Cannot install viostor driver during install win2008R2  guest os. on
> > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > found.
> > 
> > Also tried follows testing:
> > 
> > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > even though the version is the same.
> > 
> > 
> > 
> > 
> > Thanks a lot~
> > 
> > Menghuan
> 
> Hi Menghuan,
> Where did you get that virtio-win-1.9.10 from.
> FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> building process. We decided to do it mostly because we don't have a valid
> SHA-1 certificate any Longer.
> 
> Best,
> Vadim.


Hi Vadim

It will deploy the latest virtio-win build(It is virtio-win-1.9.10) when testing in libvirt team.They hit this issue.so I have a check.


Thanks

Menghuan

(In reply to Vadim Rozenfeld from comment #29)
> (In reply to menli from comment #28)
> > Hi vadim,
> > 
> > I hit a issue seems related this one, could you help to confirm if it's the
> > same  issue? thanks~
> > 
> > Cannot install viostor driver during install win2008R2  guest os. on
> > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > found.
> > 
> > Also tried follows testing:
> > 
> > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > even though the version is the same.
> > 
> > 
> > 
> > 
> > Thanks a lot~
> > 
> > Menghuan
> 
> Hi Menghuan,
> Where did you get that virtio-win-1.9.10 from.
> FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> building process. We decided to do it mostly because we don't have a valid
> SHA-1 certificate any Longer.


Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last released version in future virtio-win rpm package.
So they are still available for customers.

libvirt QE hit this issue during their testing, and we can reproduce it.
We'd like to know if the root cause is same since this bz is about netkvm driver only, we want to confirm with you if viostor is the same reason.

(In reply to lijin from comment #31)
> (In reply to Vadim Rozenfeld from comment #29)
> > (In reply to menli from comment #28)
> > > Hi vadim,
> > > 
> > > I hit a issue seems related this one, could you help to confirm if it's the
> > > same  issue? thanks~
> > > 
> > > Cannot install viostor driver during install win2008R2  guest os. on
> > > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > > found.
> > > 
> > > Also tried follows testing:
> > > 
> > > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > > even though the version is the same.
> > > 
> > > 
> > > 
> > > 
> > > Thanks a lot~
> > > 
> > > Menghuan
> > 
> > Hi Menghuan,
> > Where did you get that virtio-win-1.9.10 from.
> > FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> > building process. We decided to do it mostly because we don't have a valid
> > SHA-1 certificate any Longer.
> 
> 
> Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last
> released version in future virtio-win rpm package.
> So they are still available for customers.
> 
> libvirt QE hit this issue during their testing, and we can reproduce it.
> We'd like to know if the root cause is same since this bz is about netkvm
> driver only, we want to confirm with you if viostor is the same reason.


It is quite interesting. Yes, please give a try to any other driver, preferably 
viostor or vioscsi, because we have to fix it asap if it is a common problem.

Best,
Vadim.

(In reply to Vadim Rozenfeld from comment #32)
> (In reply to lijin from comment #31)
> > (In reply to Vadim Rozenfeld from comment #29)
> > > (In reply to menli from comment #28)
> > > > Hi vadim,
> > > > 
> > > > I hit a issue seems related this one, could you help to confirm if it's the
> > > > same  issue? thanks~
> > > > 
> > > > Cannot install viostor driver during install win2008R2  guest os. on
> > > > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > > > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > > > found.
> > > > 
> > > > Also tried follows testing:
> > > > 
> > > > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > > > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > > > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > > > even though the version is the same.
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Thanks a lot~
> > > > 
> > > > Menghuan
> > > 
> > > Hi Menghuan,
> > > Where did you get that virtio-win-1.9.10 from.
> > > FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> > > building process. We decided to do it mostly because we don't have a valid
> > > SHA-1 certificate any Longer.
> > 
> > 
> > Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last
> > released version in future virtio-win rpm package.
> > So they are still available for customers.
> > 
> > libvirt QE hit this issue during their testing, and we can reproduce it.
> > We'd like to know if the root cause is same since this bz is about netkvm
> > driver only, we want to confirm with you if viostor is the same reason.
> 
> 
> It is quite interesting. Yes, please give a try to any other driver,
> preferably 
> viostor or vioscsi, because we have to fix it asap if it is a common problem.
> 
> Best,
> Vadim.


Hi Vadim,
Network,viostor and input driver can hit this issue. vioscsi ,rng,pvpanic,balloon,serial driver work well.

(In reply to menli from comment #33)
> (In reply to Vadim Rozenfeld from comment #32)
> > (In reply to lijin from comment #31)
> > > (In reply to Vadim Rozenfeld from comment #29)
> > > > (In reply to menli from comment #28)
> > > > > Hi vadim,
> > > > > 
> > > > > I hit a issue seems related this one, could you help to confirm if it's the
> > > > > same  issue? thanks~
> > > > > 
> > > > > Cannot install viostor driver during install win2008R2  guest os. on
> > > > > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > > > > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > > > > found.
> > > > > 
> > > > > Also tried follows testing:
> > > > > 
> > > > > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > > > > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > > > > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > > > > even though the version is the same.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Thanks a lot~
> > > > > 
> > > > > Menghuan
> > > > 
> > > > Hi Menghuan,
> > > > Where did you get that virtio-win-1.9.10 from.
> > > > FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> > > > building process. We decided to do it mostly because we don't have a valid
> > > > SHA-1 certificate any Longer.
> > > 
> > > 
> > > Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last
> > > released version in future virtio-win rpm package.
> > > So they are still available for customers.
> > > 
> > > libvirt QE hit this issue during their testing, and we can reproduce it.
> > > We'd like to know if the root cause is same since this bz is about netkvm
> > > driver only, we want to confirm with you if viostor is the same reason.
> > 
> > 
> > It is quite interesting. Yes, please give a try to any other driver,
> > preferably 
> > viostor or vioscsi, because we have to fix it asap if it is a common problem.
> > 
> > Best,
> > Vadim.
> 
> 
> Hi Vadim,
> Network,viostor and input driver can hit this issue. vioscsi
> ,rng,pvpanic,balloon,serial driver work well.

Thanks a lot, Menghuan.
What is the origin of that virtio-win-1.9.10 ? 
Is it one that I have built for https://bugzilla.redhat.com/show_bug.cgi?id=1782636
or an official build ?

Best,
Vadim.

(In reply to Vadim Rozenfeld from comment #34)
> (In reply to menli from comment #33)
> > (In reply to Vadim Rozenfeld from comment #32)
> > > (In reply to lijin from comment #31)
> > > > (In reply to Vadim Rozenfeld from comment #29)
> > > > > (In reply to menli from comment #28)
> > > > > > Hi vadim,
> > > > > > 
> > > > > > I hit a issue seems related this one, could you help to confirm if it's the
> > > > > > same  issue? thanks~
> > > > > > 
> > > > > > Cannot install viostor driver during install win2008R2  guest os. on
> > > > > > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > > > > > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > > > > > found.
> > > > > > 
> > > > > > Also tried follows testing:
> > > > > > 
> > > > > > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > > > > > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > > > > > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > > > > > even though the version is the same.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Thanks a lot~
> > > > > > 
> > > > > > Menghuan
> > > > > 
> > > > > Hi Menghuan,
> > > > > Where did you get that virtio-win-1.9.10 from.
> > > > > FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> > > > > building process. We decided to do it mostly because we don't have a valid
> > > > > SHA-1 certificate any Longer.
> > > > 
> > > > 
> > > > Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last
> > > > released version in future virtio-win rpm package.
> > > > So they are still available for customers.
> > > > 
> > > > libvirt QE hit this issue during their testing, and we can reproduce it.
> > > > We'd like to know if the root cause is same since this bz is about netkvm
> > > > driver only, we want to confirm with you if viostor is the same reason.
> > > 
> > > 
> > > It is quite interesting. Yes, please give a try to any other driver,
> > > preferably 
> > > viostor or vioscsi, because we have to fix it asap if it is a common problem.
> > > 
> > > Best,
> > > Vadim.
> > 
> > 
> > Hi Vadim,
> > Network,viostor and input driver can hit this issue. vioscsi
> > ,rng,pvpanic,balloon,serial driver work well.
> 
> Thanks a lot, Menghuan.
> What is the origin of that virtio-win-1.9.10 ? 
> Is it one that I have built for
> https://bugzilla.redhat.com/show_bug.cgi?id=1782636
> or an official build ?
> 
> Best,
> Vadim.

Hi Vadim,
It is an official build,thanks.

(In reply to menli from comment #35)
> (In reply to Vadim Rozenfeld from comment #34)
> > (In reply to menli from comment #33)
> > > (In reply to Vadim Rozenfeld from comment #32)
> > > > (In reply to lijin from comment #31)
> > > > > (In reply to Vadim Rozenfeld from comment #29)
> > > > > > (In reply to menli from comment #28)
> > > > > > > Hi vadim,
> > > > > > > 
> > > > > > > I hit a issue seems related this one, could you help to confirm if it's the
> > > > > > > same  issue? thanks~
> > > > > > > 
> > > > > > > Cannot install viostor driver during install win2008R2  guest os. on
> > > > > > > Installing windows page, Load viostor Driver from virtio-win-1.9.10
> > > > > > > /viostor/2k8R2/amd64/, will report error "No signed device drivers were
> > > > > > > found.
> > > > > > > 
> > > > > > > Also tried follows testing:
> > > > > > > 
> > > > > > > Tried with virtio-win-1.9.9-3, not reproduce this issue.
> > > > > > > I check that  1.9.9-10 2k8r2 blk version is 172, 1.9.10 2k8r2 blk version is
> > > > > > > 171, both 171 and 172 work fine. Only rpm package can reproduce this issue
> > > > > > > even though the version is the same.
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > Thanks a lot~
> > > > > > > 
> > > > > > > Menghuan
> > > > > > 
> > > > > > Hi Menghuan,
> > > > > > Where did you get that virtio-win-1.9.10 from.
> > > > > > FYI, starting from build 176 we dropped off all pre-Win8 drivers drom the 
> > > > > > building process. We decided to do it mostly because we don't have a valid
> > > > > > SHA-1 certificate any Longer.
> > > > > 
> > > > > 
> > > > > Hi Vadim, we stop updating win7/2008R2 drivers, but we will still keep last
> > > > > released version in future virtio-win rpm package.
> > > > > So they are still available for customers.
> > > > > 
> > > > > libvirt QE hit this issue during their testing, and we can reproduce it.
> > > > > We'd like to know if the root cause is same since this bz is about netkvm
> > > > > driver only, we want to confirm with you if viostor is the same reason.
> > > > 
> > > > 
> > > > It is quite interesting. Yes, please give a try to any other driver,
> > > > preferably 
> > > > viostor or vioscsi, because we have to fix it asap if it is a common problem.
> > > > 
> > > > Best,
> > > > Vadim.
> > > 
> > > 
> > > Hi Vadim,
> > > Network,viostor and input driver can hit this issue. vioscsi
> > > ,rng,pvpanic,balloon,serial driver work well.

The difference between these two groups of drivers is that 

the drivers in this group are signed with a certification issued by
Symanthec (an old one) 

NetKVM/w7/amd64/netkvm.inf:18:DriverVer = 06/07/2019,61.77.104.17200
viostor/w7/amd64/viostor.inf:22:DriverVer = 06/07/2019,61.77.104.17200
vioinput/w7/amd64/vioinput.inf:21:DriverVer = 06/07/2019,61.77.104.17200

Ant all drivers in this group are signed with certificate issued by DigiCert
(more recent one)

vioscsi/w7/amd64/vioscsi.inf:21:DriverVer=08/03/2018,61.76.104.16000
viorng/w7/amd64/viorng.inf:23:DriverVer=06/11/2018,61.76.104.15400
pvpanic/w7/amd64/pvpanic.inf:22:DriverVer=06/11/2018,61.76.104.15400
Balloon/w7/amd64/balloon.inf:22:DriverVer = 03/10/2019,61.77.104.16900
vioserial/w7/amd64/vioser.inf:21:DriverVer=06/11/2018,61.76.104.15400


in any case we cannot use any of these two certifications any longer,
so there is no way to do or redo a valid sha1 cross signing.

I suggest closing this bug as wontfix.

Best,
Vadim.
   


> > 
> > Thanks a lot, Menghuan.
> > What is the origin of that virtio-win-1.9.10 ? 
> > Is it one that I have built for
> > https://bugzilla.redhat.com/show_bug.cgi?id=1782636
> > or an official build ?
> > 
> > Best,
> > Vadim.
> 
> Hi Vadim,
> It is an official build,thanks.