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.
Please retest with qemu 1.5, might be fixed meanwhile.
In case it still fails: What happens exactly? Guest refuses to suspend? Guest fails to resume? qemu crashes? Something else?
Is the usb-storage needed to trigger or do you see failures with xhci alone too?
Test with qemu-kvm-1.5.0-2.el7.x86_64 and kernel 3.10.0-0.rc2.57.el7.x86_64 both in guest and host, this time S3/S4 won't even work without xhci, it's hard to tell what's the problem since there are tens of S3/S4 bugs, i will re-test this one after S3/S4 works again, keeps the needinfo set.
(In reply to Gerd Hoffmann from comment #8)
> (In reply to Gerd Hoffmann from comment #5)
> > Ping, s3 seems to work meanwhile (at least with "-M pc").
> > Please see comment #2 and retest.
>
> Ping²
Hi Shu,
Can you have a try and update the testing result in the bz?
Best Regards,
Junyi
Tried with command line in comment0, with:
-device nec-usb-xhci,id=xhci -drive file=disk,if=none,id=drive-usb-0-0,media=disk,format=qcow2,cache=none,aio=native -device usb-storage,drive=drive-usb-0-0,id=usb-0-0,removable=on,bus=xhci.0,port=1 -device usb-ehci,id=ehci -drive file=disk2,if=none,id=drive-usb-0-1,media=disk,format=qcow2,cache=none,aio=native -device usb-storage,drive=drive-usb-0-1,id=usb-0-1,removable=on,bus=ehci.0,port=1 -usb -device usb-tablet,id=input1,bus=usb-bus.0,port=1 -device usb-hub,bus=usb-bus.0,port=2,id=hub
guest fails to recover from S4
without Usb related command line, guest recovers from S4 correctly.
Please retest with this test build:
http://people.redhat.com/ghoffman/bz1103193/
(probably doesn't change anything, test build has a bunch of usb fixes but
nothing s4 related, but who knows, doesn't hurt to check ...)
What does "fails to recover" mean exactly?
Guest dead? Only USB broken? Something else?
(In reply to Gerd Hoffmann from comment #12)
> Please retest with this test build:
> http://people.redhat.com/ghoffman/bz1103193/
>
> (probably doesn't change anything, test build has a bunch of usb fixes but
> nothing s4 related, but who knows, doesn't hurt to check ...)
>
> What does "fails to recover" mean exactly?
> Guest dead? Only USB broken? Something else?
Boot guest again, guest restarts instead of recovering from hibernate.