Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Steps to Reproduce:
When test SVVP for RHEL6.3 ,PCI Hardware Compliance Test For Systems failed in task Process Logged Messages,there are 4 failures in whole except for the Root BUS has a Errata.Details is described in the failure log files attached.
Version-Release number of selected component (if applicable):
Kernel-2.6.32-330.el6.x86_64
qemu-kvm-0.12.1.2-2.307.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare the SVVP test Environment
2.Add 10 windows 2012 guests in one machine,create a submission for SVVP ,select the MC ,SC and SUT, the sut use e1000 network
3. Run PCI Hardware Compliance Test For Systems job
Actual results:
job prompts some warnings
Expected results:
job should pass
Additional info :
ok this is the warning:
<Warn ^M
File="<Unspecified file>" ^M
Line="0" ^M
UserText="Assertion 5CB2102-1603-4ACE-8A03-FFD777E987F0: Failed with a WARNING. Bit 10 (Interrupt Disable) in the Command register (offset 4h) in the Header table must be read-writable if the device supports an interrupt." CA="835907" LA="840327" >^M
<rti id="3124255527" />^M
<ctx id="1406515444" />^M
</Warn>^M
This warning is too risky to fix for 6.4. Fixed upstream
commit a7b15a5cc6261629879d4d8a71bacf23f983000b .
Assuming that for SVVP it is just a warning, postponed to RHEL6.5.
The backport is simple, but making migration to older RHEL versions properly work with this bit is too complex for the current 6.4 stage.
Steps to Reproduce: When test SVVP for RHEL6.3 ,PCI Hardware Compliance Test For Systems failed in task Process Logged Messages,there are 4 failures in whole except for the Root BUS has a Errata.Details is described in the failure log files attached. Version-Release number of selected component (if applicable): Kernel-2.6.32-330.el6.x86_64 qemu-kvm-0.12.1.2-2.307.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare the SVVP test Environment 2.Add 10 windows 2012 guests in one machine,create a submission for SVVP ,select the MC ,SC and SUT, the sut use e1000 network 3. Run PCI Hardware Compliance Test For Systems job Actual results: job prompts some warnings Expected results: job should pass Additional info : ok this is the warning: <Warn ^M File="<Unspecified file>" ^M Line="0" ^M UserText="Assertion 5CB2102-1603-4ACE-8A03-FFD777E987F0: Failed with a WARNING. Bit 10 (Interrupt Disable) in the Command register (offset 4h) in the Header table must be read-writable if the device supports an interrupt." CA="835907" LA="840327" >^M <rti id="3124255527" />^M <ctx id="1406515444" />^M </Warn>^M This warning is too risky to fix for 6.4. Fixed upstream commit a7b15a5cc6261629879d4d8a71bacf23f983000b .