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.
It looks like this will require QEMU changes. I'll take a look.
Comment 8Yvugenfi@redhat.com
2016-11-27 07:27:12 UTC
(In reply to Ladi Prosek from comment #7)
> It looks like this will require QEMU changes. I'll take a look.
I think Marchel already started to fix it. Better ask him: Marcel Apfelbaum <marcel>
(In reply to Yan Vugenfirer from comment #8)
> (In reply to Ladi Prosek from comment #7)
> > It looks like this will require QEMU changes. I'll take a look.
>
> I think Marchel already started to fix it. Better ask him: Marcel Apfelbaum
> <marcel>
Thanks, QEMU's PCIe devices (and virtio PCIe in particular) really are out of spec in terms of error reporting, power management, and more.
Marcel, please let me know if this is already worked on and if I can help in any way. Thanks!
Comment 10Marcel Apfelbaum
2016-11-28 13:24:49 UTC
(In reply to Ladi Prosek from comment #9)
> (In reply to Yan Vugenfirer from comment #8)
> > (In reply to Ladi Prosek from comment #7)
> > > It looks like this will require QEMU changes. I'll take a look.
> >
> > I think Marchel already started to fix it. Better ask him: Marcel Apfelbaum
> > <marcel>
>
> Thanks, QEMU's PCIe devices (and virtio PCIe in particular) really are out
> of spec in terms of error reporting, power management, and more.
>
Hi Ladi,
> Marcel, please let me know if this is already worked on and if I can help in
> any way. Thanks!
I have received from Gal a way to reproduce the tests, I intend to
run them this week. I'll let you know if I need help.
Thanks,
Marcel
Comment 11Marcel Apfelbaum
2017-01-05 11:30:44 UTC
Tried this issue with qemu-kvm-rhev-2.9.0-1.el7 under q35, it also failed(3/3).
Used version:
kernel-3.10.0-657.el7.x86_64
qemu-kvm-rhev-2.9.0-1.el7.x86_64
seabios-1.10.2-2.el7.x86_64
virtio-win-prewhql-136
Best regards~
Peixiu
(In reply to Peixiu Hou from comment #15)
> Tried this issue with qemu-kvm-rhev-2.9.0-1.el7 under q35, it also
> failed(3/3).
Peixiu Hou, can you please attach the logs? Thanks!
(In reply to Ladi Prosek from comment #16)
> (In reply to Peixiu Hou from comment #15)
> > Tried this issue with qemu-kvm-rhev-2.9.0-1.el7 under q35, it also
> > failed(3/3).
>
> Peixiu Hou, can you please attach the logs? Thanks!
Hi Ladi,
I rerun it with win8-32 and qemu-kvm-rhev-2.9.0-1.el7 under q35, it can be passed.
And comment#15 result is for win2008-32, although it failed, but it can be filter passed.
Best Regards~
Peixiu
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
Created attachment 1218361 [details] failed logs Description of problem: job "PCI Hardware Compliance Test For a Single Device(PCIHCT)" fail w/ "-M q35" influence OS: win2008,win2008R2,win7, win8 and win8.1 Version-Release number of selected component (if applicable): virtio-win-prewhql-128 qemu-kvm-rhev-2.6.0-27.el7.x86_64 kernel-3.10.0-518.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot w/ "-M q35" and pcie device /usr/libexec/qemu-kvm -name 128SRLWIN832JTU -enable-kvm -m 3G -smp 4 -uuid 9c0b7b6e-9beb-44ea-b1a2-72e541349142 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/128SRLWIN832JTU,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=128SRLWIN832JTU,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_8_enterprise_x86_dvd_917587.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=128SRLWIN832JTU.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:4a:6e:12:1a -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga cirrus -M q35 -device ioh3420,bus=pcie.0,id=root1.0,slot=1 -device virtio-serial-pci,id=serial0,bus=root1.0 -chardev socket,id=serialchardev0,path=/tmp/128SRLWIN832JTU_port0,server,nowait -device virtserialport,id=port0,chardev=serialchardev0,bus=serial0.0 2. run job "PCI Hardware Compliance Test For a Single Device(PCIHCT)" Actual results: Failed Expected results: Pass Additional info: It can pass with "-M pc"