Bug 872573
| Summary: | dompmsuspend doesn't work twice | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Kamil Páral <kparal> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | berrange, clalancette, crobinso, itamar, jdenemar, jforbes, jtomko, laine, libvirt-maint, rbalakri, shyu, veillard, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-16 17:29:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kamil Páral
2012-11-02 13:13:23 UTC
I have to power off the guest to get it working again. Rebooting the guest is not enough. Well, I think this works as expected. If you suspend a guest OS to memory, all you can do with it is resume or power off. You don't expect anything else from your laptop after suspending it to memory, do you? The only bug I see is that the error message is quite unclear. We should be able to tell that the guest is already suspended. No, you don't understand. suspend -> resume # works suspend -> resume -> suspend # doesn't work suspend -> resume -> power off -> start -> suspend -> resume # works Ah, I thought there was no resume between the two suspends. Is the guest otherwise working after resume? Can you ssh to it, for example? Yes, the guest was working after the resume just fine. I didn't try ssh, but I could use GNOME as usual. But I couldn't suspend it again. Multiple suspend -> resume -> suspend cycles worked for me when testing this fix:
commit 723522328f2d92e4c2d5de35b3b3ec0302bb06ac
Author: Ján Tomko <jtomko>
AuthorDate: 2015-02-26 14:00:47 +0100
Commit: Ján Tomko <jtomko>
CommitDate: 2015-03-02 08:07:56 +0100
Check if domain is running in qemuDomainAgentIsAvailable
If the domain is not running, the agent will not respond.
Do not even try.
https://bugzilla.redhat.com/show_bug.cgi?id=872424
git describe: v1.2.13-20-g7235223
It will be a part of the next upstream release.
|