Description of problem: After install xenpv-win,use everest tool to look at the hardware address of RedHat PV NIC Driver,the address is not correct. Version-Release number of selected component (if applicable): xenpv-win-32-bit-1.0.0-1.el5.noarch.rpm How reproducible: always Steps to Reproduce: 1.Install the xenpv-win-32-bit according to the installation manual 2.Look at the hardware address of RedHat PV NIC Driver with everest or other tools. Actual results: The hardware id is SCSI\Net____RHEL____________NIC0001 Expected results: The hardware is should be VEN &DEV &SUBSYS &REV Additional info:
Redhat VirtIO NIC has hardware id:PCI\VEN_1AF4&DEV_1000&SUBSYS_00011AF4&REV_00
Created attachment 335198 [details] the PNP of virtIO
Created attachment 335199 [details] the PNP of Redhat NIC
http://www.wd-3.com/archive/InfFiles.htm The above link gives a nice description on INF files. The PnP ID is defined in the INF file. Windows Installer Reads this INF file and installs the driver according to the rules defined in the file. According to the above tutorial link, PnP ID can be a Hardware ID or Compatible ID. The ID here is a Compatible ID.
PnP ID is correct, is there any other repercussion which stops certification?
Hi, ashok,I have retested again with WLK 1.2 about oem0.inf and oem1.inf. After applying filter,they can pass Run INFTest against a single INF,Plug and Play Driver Test,Device Path Exerciser. You are right "According to the above tutorial link, PnP ID can be a Hardware ID or Compatible ID. The ID here is a Compatible ID." So it is not a bug.
Thanks, for re testing, and updates. as per C#6 it can be closed.
Thanks for the confirmation. Resolving as NOTABUG.