On 03/11/2012 11: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. It won't. To wake up a guest in S3 suspension, you need the pmwakeup command, or else a timer or input device wakeup trigger. 'virsh resume' only wakes up a paused guest, not a power-management suspended guest. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list