Re: [libvirt-users] libvirt-users Digest, Vol 52, Issue 39
On 04/27/2014 10:42 AM, Taimur Al Said wrote:
On Sun, Apr 27, 2014 at 5:00 PM,
<libvirt-users-request(a)redhat.com> wrote:
> Send libvirt-users mailing list submissions to
> libvirt-users(a)redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/libvirt-users
> or, via email, send a message with subject or body 'help' to
> libvirt-users-request(a)redhat.com
>
> You can reach the person managing the list at
> libvirt-users-owner(a)redhat.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of libvirt-users digest..."
Please follow the advice that you were given, by NOT replying directly
to an entire digest message.
I guess my query was clear. However, I'll make it clearer.
I know that the such events are caused by the hypervisor. Either directly
or using tools such as Libvirt. The question is: can such events be
detectable from the VM level? In another word, can the VM tell if it was
being paused/rebooted/migrated/etc?
If you want to inform the VM that it has been paused, then it is up to
you to wire up that communication channel. For example, the qemu guest
agent includes a set-time command that allows a hypervisor to tell the
guest to recheck its notion of the current time, useful for getting the
guest to sync back to the current time after the hypervisor has resumed
the guest from sleep. But it still leaves the burden on the management
application to invoke this guest-agent command at the right sequence
points; it's not something that libvirt will automate.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Attachments:
- signature.asc (application/pgp-signature — 604 bytes)