[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] Start of freeze for libvirt-0.9.10 and availability of rc1
- From: Michal Privoznik <mprivozn redhat com>
- To: Eric Blake <eblake redhat com>
- Cc: libvir-list redhat com
- Subject: Re: [libvirt] Start of freeze for libvirt-0.9.10 and availability of rc1
- Date: Fri, 10 Feb 2012 09:44:37 +0100
On 10.02.2012 00:32, Eric Blake wrote:
> On 02/06/2012 12:21 AM, Daniel Veillard wrote:
>> We are now entering the freeze for libvirt-0.9.10
>> Hopefully all the API changes needed for that version are
>> already commited to git head.
>>
>> I have made a release candidate 1 tarball (and associated rpms) at
>> ftp://libvirt.org/libvirt/libvirt-0.9.10-rc1.tar.gz
>> and the git tree is tagged.
>>
>> I think I will make an release candidate 2 tarball on Wednesday, and
>> I'm hoping for a final release next Monday the 13th.
>>
>> Please give it a try !
>
> I'm wondering if we're too late for one more API to round out the API we
> added in this release. Qemu is proposing a new monitor command
> system_wakeup which lets the host inject a power-button wakeup to a
> guest that has gone into S3 sleep. Since we added the
> virDomainPMSuspendForDuration command to put the guest into S3 from the
> host, I think we need a counterpart API that wakes the guest back up,
> rather than relying on mouse clicks, serial input, or timeouts doing the
> job for us. It's a shame that virDomainResume() has no flags argument,
> and that it is already tied to virDomainSuspend() (aka guest pause), so
> I'm thinking something like:
>
> /* Inject a wakeup into the guest that previously used
> * virDomainPMSuspendForDuration, rather than waiting for the
> * previously requested duration (if any) to elapse. */
> int virDomainPMWakeup(virDomainPtr dom, unsigned int flags);
>
I'd like to see this API in as well.
Michal
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]