Bug 2016291

Summary: [virtio-win] NetKVM: INF warning during the build of the driver
Product: Red Hat Enterprise Linux 9 Reporter: Yvugenfi <yvugenfi>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
virtio-win sub component: virtio-win-prewhql QA Contact: leidwang <leidwang>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: lijin
Version: 9.0Keywords: RFE, TestOnly
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:35:27 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:

Description Yvugenfi@redhat.com 2021-10-21 08:19:28 UTC
Description of problem:
During the build there is a warning:
warning 1324: [Version] section should specify PnpLockdown=1.

To fix it PnpLockdown=1 should be added to INF file.
This will instruct Windows OS to protect drivers binaries:
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/version-section-in-a-network-inf-file


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yvugenfi@redhat.com 2021-10-21 08:21:14 UTC
Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/664

Comment 3 leidwang@redhat.com 2021-11-03 08:23:22 UTC
Hi Yan,

It seems that the fix has been merged and included in build 213. Maybe you need to change the status and add the fix version.

By the way, what should I do to verify this bz? Judging from comment 0, this fix is just to avoid warnings during the build process.

Thanks!

Comment 4 Yvugenfi@redhat.com 2021-11-03 10:05:32 UTC
(In reply to leidwang from comment #3)
> Hi Yan,
> 
> It seems that the fix has been merged and included in build 213. Maybe you
> need to change the status and add the fix version.
> 
> By the way, what should I do to verify this bz? Judging from comment 0, this
> fix is just to avoid warnings during the build process.
> 
> Thanks!

Yes. It is just a warning.

The fix should be included in build 214 (I think maybe even in 213).

To test you can check if there is this warning in the build logs.
For example in 211 the warning exists (grep for "PnpLockdown"):
http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/virtio-win-prewhql/0.1/211/data/logs/win/build.log

But doesn't exist in 214:
http://download.eng.bos.redhat.com/brewroot/vol/rhel-9/packages/virtio-win-prewhql/0.1/214/data/logs/win/build.log

Comment 5 leidwang@redhat.com 2021-11-03 10:14:17 UTC
(In reply to Yvugenfi from comment #4)
> (In reply to leidwang from comment #3)
> > Hi Yan,
> > 
> > It seems that the fix has been merged and included in build 213. Maybe you
> > need to change the status and add the fix version.
> > 
> > By the way, what should I do to verify this bz? Judging from comment 0, this
> > fix is just to avoid warnings during the build process.
> > 
> > Thanks!
> 
> Yes. It is just a warning.
> 
> The fix should be included in build 214 (I think maybe even in 213).
> 
> To test you can check if there is this warning in the build logs.
> For example in 211 the warning exists (grep for "PnpLockdown"):
> http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/virtio-win-
> prewhql/0.1/211/data/logs/win/build.log
> 
> But doesn't exist in 214:
> http://download.eng.bos.redhat.com/brewroot/vol/rhel-9/packages/virtio-win-
> prewhql/0.1/214/data/logs/win/build.log

Okay, there is no warning in the build log of 214(warning 1324: [Version] section should specify PnpLockdown=1.)
So set the status to VERIFIED.Thanks!

Comment 8 errata-xmlrpc 2022-05-17 15:35:27 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 (new packages: virtio-win), 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/RHBA-2022:3890