Red Hat Bugzilla – Bug 868240
[WHQL][balloon]two warnings when running DevFund INF Test job for win8/win2012
Last modified: 2014-06-13 05:24:44 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start VM with balloon
2.running dev fund inf job
two warnning about balloon driver
1.Driver package C:\Windows\Inf\oem1.inf specifies LoadOrderGroup for registration of service BALLOON display name "VirtIO Balloon Service". This is not recommended.
2.Driver package C:\Windows\Inf\oem1.inf does not use PnpLockdown directive in its version section. It is recommended to specify PnpLockdown = 1 in the version section.
not a testblocker
Is this test run on the other drivers too? Because I see that the virtio-serial's inf file include the LoadOrderGroup directive and doesn't have PnpLockdown as well.
(In reply to comment #2)
> Is this test run on the other drivers too? Because I see that the
> virtio-serial's inf file include the LoadOrderGroup directive and doesn't
> have PnpLockdown as well.
I Tried w/ serial on build 51 .hit the exactly same issue .
But this bug is not urgent as HCk accepts warnings
A patch which updated both serial and balloon's inf files was posted.
Re-Test this issue on virtio-win-prewhql-75
Warnings on BALLOON display name is fixed ald .
But it still shows following infos in the log file
Running test on driver INF C:\Windows\Inf\oem1.inf
Warning 3/20/2014 6:32:51.684 AM Driver package C:\Windows\Inf\oem1.inf does not use PnpLockdown directive in its version section. It is recommended to specify PnpLockdown = 1 in the version section.
File: Line: -1
End Test 3/20/2014 6:32:51.684 AM DevFundInfTest::UsePnpLockdown
Based on above ,this issue has not been fixed yet
Reassign this issue
Although the MSDN's documentation state that it is possible for the PnpLockdown value to be 0 to maintain backward compatibility, I've posted a set of patches which change the value to 1 for balloon, serial and rng.
Vadim thinks that this change might affect the installer's behavior during an upgrade. Can you please verify it? Thanks.
(In reply to Gal Hammer from comment #12)
> Vadim thinks that this change might affect the installer's behavior during
> an upgrade. Can you please verify it? Thanks.
I tried driver upgrade from build71 to build79 ,did not find any issue
QE Re-test the bug on build 79 on win2012/2012R2/win832/win864 OS
Now,all warnings were gone from the logs and the job also could pass smoothly.so the issue has been fixed.Thanks.
Move status to VERiFied according to comment #14
Ronen , QE request thsi for rhel7.0.z
(In reply to Mike Cao from comment #17)
> Ronen , QE request thsi for rhel7.0.z
My bad .PM clone it ald
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.