On 03/12/2012 01:13 PM, Osier Yang wrote:
On 03/11/2012 10:37 PM, Paolo Bonzini wrote:
Il 05/03/2012 11:25, Osier Yang ha scritto:
This introduces a new paused reason VIR_DOMAIN_PAUSED_SUSPEND,
and new suspend event type VIR_DOMAIN_EVENT_SUSPENDED_SUSPEND.
While a SUSPEND event occurs, the running domain status will be
transferred to "paused" with reason "VIR_DOMAIN_PAUSED_SUSPEND",
and a new domain lifecycle event emitted with type
VIR_DOMAIN_EVENT_SUSPENDED_SUSPEND.
---
Does "virsh resume" correctly wakeup such a domain?
Ah, yes, I prohibited the situation waking up a domain which
wasn't paused by SUSPEND event. But here I forgot it.
If not, perhaps a
different state should be added so that "virsh resume" can look at the
state and issue the appropriate monitor command (or alternatively, it
could be considered a QEMU bug).
We have the paused reason. And the patch which should be
squashed in in the attachment.
But I'm interested in trying if "virsh resume" wakeup a
domain pasued by SUSPEND event.
Tried, and the guest paused by "pm-suspend" inside guest can't
be waken up successfully using "virsh resume". (the guest actually
is still paused, but "virsh resume" will change the domain status
into "running"). That's not what we want.
Osier
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list