Bug 1633087
| Summary: | [virtio-win] incorrect virtio-win driver version shown in sigverif log file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Peixiu Hou <phou> | ||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||
| virtio-win sub component: | distribution | QA Contact: | Peixiu Hou <phou> | ||||||
| Status: | CLOSED WONTFIX | Docs Contact: | |||||||
| Severity: | medium | ||||||||
| Priority: | medium | CC: | ailan, lijin, phou, rbalakri, virt-bugs, vrozenfe | ||||||
| Version: | 8.0 | Keywords: | Reopened | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-07-12 07:30:08 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1682882 | ||||||||
| Bug Blocks: | 1658880 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1487053 [details]
SIGVERIF-win8.1-64.TXT
On win8.1-64, only the balloon driver version is not correct, others driver version are correct.
phou, Could you verify this bug with latest 163 version? Thanks I'm afraid that this issue has not been fixed properly yet. Going to run a new build soon and let you know. Best regards, Vadim. Can we please check if viostor.inf file from the latest (b163) build still has this problem? Thanks, Vadim. (In reply to Vadim Rozenfeld from comment #6) > Can we please check if viostor.inf file from the latest (b163) build still > has this problem? > Hi Vadim, I tested on win8-32 guest, also can reproduce this issue on viostor driver with latest build 163. Best Regards~ Peixiu With build 163 status as follows: [c:\windows\system32] streamci.dll 7/26/2012 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows viorngci.dll 12/12/2018 <dbf4>ɛ Signed viorng.cat Red Hat, Inc. viorngum.dll 12/12/2018 <dbf4>ɛ Signed viorng.cat Red Hat, Inc. wdfcoinstaller01011. 11/28/2018 <dbf4>ɛ Signed vioser.cat Red Hat, Inc. [c:\windows\system32\drivers] acpi.sys 7/26/2012 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows agilevpn.sys 7/26/2012 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-SKMicrosoft Windows asyncmac.sys 7/26/2012 2:5.1,2:5.2,2:6.0,2:Signed Microsoft-Windows-SKMicrosoft Windows balloon.sys 12/12/2018 <dbf4>ɛ Signed balloon.cat Red Hat, Inc. viohidkmdf.sys 12/12/2018 <dbf4>ɛ Signed vioinput.cat Red Hat, Inc. vioinput.sys 12/12/2018 <dbf4>ɛ Signed vioinput.cat Red Hat, Inc. viorng.sys 12/12/2018 <dbf4>ɛ Signed viorng.cat Red Hat, Inc. vioscsi.sys 11/28/2018 <dbf4>ɛ Signed vioscsi.cat Red Hat, Inc. vioser.sys 12/12/2018 <dbf4>ɛ Signed vioser.cat Red Hat, Inc. viostor.sys 12/12/2018 <dbf4>ɛ Signed viostor.cat Red Hat, Inc. netkvm.sys 12/12/2018 <dbf4>ɛ Signed netkvm.cat Red Hat, Inc. pci.sys 7/26/2012 2:5.1 Signed Microsoft-Windows-CoMicrosoft Windows pvpanic.sys 12/12/2018 <dbf4>ɛ Signed pvpanic.cat Red Hat, Inc. 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. Hi vadim, This issue was closed by suto, I'm not sure if you've evaluate this issue, if not, could you help to evaluate it? For QE's testing, it also can be triggered on the latest version. 1. Reproduced this bug with latest virtio-win-1.9.15-0. 2. Tried on openstack platform, this issue can be reproduced as well. Used version: kernel-4.18.0-240.5.1.el8_3.x86_64 qemu-kvm-5.1.0-15.module+el8.3.1+8772+a3fdeccd.x86_64 virtio-win-1.9.15-0.el8 seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64 Thanks a lot~ Peixiu (In reply to Peixiu Hou from comment #17) > Hi vadim, > > This issue was closed by suto, I'm not sure if you've evaluate this issue, > if not, could you help to evaluate it? > > For QE's testing, it also can be triggered on the latest version. > 1. Reproduced this bug with latest virtio-win-1.9.15-0. > 2. Tried on openstack platform, this issue can be reproduced as well. > > Used version: > kernel-4.18.0-240.5.1.el8_3.x86_64 > qemu-kvm-5.1.0-15.module+el8.3.1+8772+a3fdeccd.x86_64 > virtio-win-1.9.15-0.el8 > seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64 > > Thanks a lot~ > Peixiu Let's keep this issue open for a while. Thanks, Vadim. Hi vadim, For this issue, If you have not plan to fix it in the future, I can accept close it. It's not a high level issue and it seems the issue does not impact business of our customer~ Thanks～ Peixiu (In reply to Peixiu Hou from comment #21) > Hi vadim, > > For this issue, If you have not plan to fix it in the future, I can accept > close it. > It's not a high level issue and it seems the issue does not impact business > of our customer~ > > > Thanks～ > Peixiu Hi Peixiu, IIRC this problem happend on Win8 platforms only, right? If so, then let's close it since it simms to be some internal Win8 problem fixed in more recent Windows versions. Best regards, Vadim. (In reply to Vadim Rozenfeld from comment #22) > (In reply to Peixiu Hou from comment #21) > > Hi vadim, > > > > For this issue, If you have not plan to fix it in the future, I can accept > > close it. > > It's not a high level issue and it seems the issue does not impact business > > of our customer~ > > > > > > Thanks～ > > Peixiu > > Hi Peixiu, > IIRC this problem happend on Win8 platforms only, right? > If so, then let's close it since it simms to be some > internal Win8 problem fixed in more recent Windows versions. > Hi vadim, Sorry for reply late, no, it's not only happens on win8~ I tried to test on win8.1-32, win8.1-64 and win2012-64 guest vm, all reproduced this issue. And I also tried on win10-32, win10-64, win2022 and win2012-r2 guest, not reproduce this issue. Thanks~ Peixiu > Best regards, > Vadim. 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. |
Created attachment 1487052 [details] SIGVERIF-win8-64.TXT Description of problem: On win8-64 guest, run sigverif from cmd in guest, check the sigverif log(as attachments SIGVERIF-win8-64.TXT) found: all drivers version shown as *.cat. ================================================================================ File Modified Version Status Catalog Signed By ------------------ ------------ ----------- ------------ [c:\windows\system32] balloon.sys 8/25/2018 n.cat Signed balloon.cat Microsoft Windows Hardware Compatibility Publisher netkvm.sys 8/25/2018 cat Signed netkvm.cat Microsoft Windows Hardware Compatibility Publisher pvpanic.sys 6/12/2018 c.cat Signed pvpanic.cat Microsoft Windows Hardware Compatibility Publisher viohidkmdf.sys 7/6/2018 put.cat Signed vioinput.cat Microsoft Windows Hardware Compatibility Publisher vioinput.sys 7/6/2018 put.cat Signed vioinput.cat Microsoft Windows Hardware Compatibility Publisher viorng.sys 6/12/2018 cat Signed viorng.cat Microsoft Windows Hardware Compatibility Publisher vioscsi.sys 8/25/2018 i.cat Signed vioscsi.cat Microsoft Windows Hardware Compatibility Publisher vioser.sys 6/12/2018 cat Signed vioser.cat Microsoft Windows Hardware Compatibility Publisher viostor.sys 8/25/2018 r.cat ============================================================================== On win8.1-64 guest, run sigverif from cmd in guest, checked the sigverif log(as attachments SIGVERIF-win8.1-64.TXT) found: except balloon driver, all others version shown as their product version. ====================================================================================================================================================== File Modified Version Status Catalog Signed By ------------------ ------------ ----------- ------------ ----------- ------------------- [c:\windows\system32] balloon.sys 8/25/2018 None Signed balloon.cat Microsoft Windows Hardware Compatibility Publisher netkvm.sys 8/25/2018 63.76.104.16000 Signed netkvm.cat Microsoft Windows Hardware Compatibility Publisher pvpanic.sys 8/25/2018 62.76.104.15400 Signed pvpanic.cat Microsoft Windows Hardware Compatibility Publisher viohidkmdf.sys 8/25/2018 62.76.104.15600 Signed vioinput.cat Microsoft Windows Hardware Compatibility Publisher vioinput.sys 8/25/2018 62.76.104.15600 Signed vioinput.cat Microsoft Windows Hardware Compatibility Publisher viorng.sys 8/25/2018 62.76.104.15400 Signed viorng.cat Microsoft Windows Hardware Compatibility Publisher vioscsi.sys 8/25/2018 62.76.104.16000 Signed vioscsi.cat Microsoft Windows Hardware Compatibility Publisher vioser.sys 8/25/2018 62.76.104.15400 Signed vioser.cat Microsoft Windows Hardware Compatibility Publisher viostor.sys 8/25/2018 62.76.104.15800 Signed viostor.cat Microsoft Windows Hardware Compatibility Publisher Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Boot a guest up with all virtio devices. -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0,vhost=on,queues=4 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:52:3b:35:88:00,mq=on,vectors=10 \ -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 \ -device virtio-balloon-pci,id=balloon0 \ -device pvpanic,id=pvpanic0,ioport=0x0505 \ -drive file=blk-disk.raw,if=none,id=drive-virtio-disk0,format=raw,serial=mike_cao,cache=none -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0 \ -device virtio-scsi-pci,id=scsi1 -drive file=scsi-disk.raw,if=none,id=drive-scsi-disk1,format=raw,serial=mike_cao,cache=none -device scsi-hd,bus=scsi1.0,drive=drive-scsi-disk1,id=scsi-disk1 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 \ 2. Install drivers for all virtio devices. 3. Open cmd, run sigverif. 4. Check the sigverif log file. Actual results: driver's version shown incorrect, as *.cat or None Expected results: driver's version shown as their correct version, like netkvm.sys should be 63.76.104.16000 Additional info: Also reproduced this issue on win2012 guest.