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.
Description of problem:
The issue occurs on both wn2k3-32 and win2k3-64 guest.
Plug and Play job failed on win2k3-32 and wink3-64 OS due to PNPTryStopDeviceAndFailRestart and PNPSurpriseRemoveAndRestartDevice
Version-Release number of selected component (if applicable):
build70
kernel-414
qemu-kmv-rhev-397
How reproducible:
5 times
Steps to Reproduce:
1.boot up guest with the following CLI
...
/usr/libexec/qemu-kvm \
-M rhel6.5.0 \
-m 2G \
-smp 4,cores=4 \
-cpu cpu64-rhel6,+x2apic,family=0xf \
-usb \
-device usb-tablet \
-drive file=win2k3-32-serial.raw,if=none,id=drive-ide0-0-0,format=raw,rerror=stop,werror=stop,cache=none \
-device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0-0,bootindex=1 \
-netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no \
-device e1000,netdev=hostnet0,mac=00:31:32:c1:a3:31,id=net0 \
-uuid a0c24c48-0e84-4bb2-bc23-02cda4c2bc93 \
-no-kvm-pit-reinjection \
-chardev socket,id=111a,path=/tmp/monitor-win2k3-32-serial-70,server,nowait \
-mon chardev=111a,mode=readline \
-name win2k3-32-serial-70 \
-vnc :1 \
-vga cirrus \
-rtc base=localtime,clock=host,driftfix=slew \
-device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 \
-chardev socket,id=channel0,path=/tmp/tt,server,nowait \
-device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0 \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=0 \
-monitor stdio
done
...
2.submit the jobs
3.
Actual results:
The job always failed
Expected results:
The job can pass
Additional info:
Will upload the hck logs to the bug
(In reply to Gal Hammer from comment #3)
> Which version of the WHQL tests suite is it?
HCK2.0 . I think this is a known issue . Run this job without virtserialport can workaound it
Mike
Comment 5RHEL Program Management
2013-10-14 01:55:52 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
As we have upgrade hck2.0 to hck2.1 and win2k3 cannot install hck2.1 client correctly,I ran this job on WLK.
I failed to reproduce this issue,both with build70 and build74,this job can pass without any error.
package info:
qemu-kvm-rhev-1.5.3-30.el7.x86_64
kernel-3.10.0-64.el7.x86_64
seabios-1.7.2.2-7.el7.x86_64
Good to hear, as WHQL certification for Windows XP, 2003 and 2008 (not R2) are tested using WLK and not HCK 2.1.
Moving to QE for verification and closer.
Thanks!
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.