RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1444271 - [virtio-win][viorng]job "DF - InfVerif INF Verification" failed on HLK 1703
Summary: [virtio-win][viorng]job "DF - InfVerif INF Verification" failed on HLK 1703
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Ladi Prosek
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-21 03:16 UTC by lijin
Modified: 2017-08-01 12:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 12:58:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
win10-64 rng hlk 1703 log (4.98 MB, application/zip)
2017-04-21 03:16 UTC, lijin
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2341 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2017-08-01 16:52:38 UTC

Description lijin 2017-04-21 03:16:06 UTC
Created attachment 1273142 [details]
win10-64 rng hlk 1703 log

Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1.boot win10-64 guest with rng device:
/usr/libexec/qemu-kvm -name 135RNGW10D64I7B -enable-kvm -m 3G -smp 4 -uuid 65a9178f-8066-4884-b122-a157ee30cedc -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/135RNGW10D64I7B,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -drive file=135RNGW10D64I7B,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=135RNGW10D64I7B.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:1c:58:32:9d -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga std -M pc -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,id=rng1,bus=pci.0

2.submit job

Actual results:
job failed as:
Error 4/19/2017 11:08:57.317 PM Code 1209, C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e0bbf44aa3753b55\viorng.inf line 25: Section [destinationdirs] is defined multiple times. 
Error 4/19/2017 11:08:57.319 PM Code 1209, C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e0bbf44aa3753b55\viorng.inf line 31: Section [sourcedisksfiles] is defined multiple times.  
Error 4/19/2017 11:08:57.320 PM Code 1209, C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e0bbf44aa3753b55\viorng.inf line 45: Section [virtrng_device.nt] is defined multiple times. 


Expected results:
job can pass

Additional info:
this job can pass with HLK 1607

Comment 1 lijin 2017-04-26 07:03:48 UTC
I guesss balloon/serial/pvpanic/input will all hit the same issue as I check the .inf file,destinationdirs/sourcedisksfiles are defined multiple times.

On old test suit(HLK 1607),this job can pass.

Comment 2 Ladi Prosek 2017-04-26 13:45:52 UTC
(In reply to lijin from comment #1)
> I guesss balloon/serial/pvpanic/input will all hit the same issue as I check
> the .inf file,destinationdirs/sourcedisksfiles are defined multiple times.
> 
> On old test suit(HLK 1607),this job can pass.

Indeed, balloon/serial/pvpanic/input have issues too. They are reported as warnings by the ChkINF tool (part of WDK). Not sure why they suddenly became blockers in the new HLK.

Posted a pull request with fixes for all affected INF files:
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/129

Comment 3 Ladi Prosek 2017-05-02 04:39:12 UTC
viorng.inf is fixed in
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/129/commits/3b4643859a65d2c9dcd22f46b9641e43f3da04ef

balloon in 9d12a62
pvpanic in d93862d
vioserial in 8a7b51e
vioinput in 08112bc

Comment 4 lijin 2017-05-26 06:00:51 UTC
job pass with build137 and pass the certification,so change status to verified

Comment 7 errata-xmlrpc 2017-08-01 12:58:08 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, 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-2017:2341


Note You need to log in before you can comment on or make changes to this bug.