[libvirt] Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2)

libvirt could open a second monitor connection to qemu, and in the second one execute "wait_event". When the watchdog triggers, the wait command would print the event, libvirt would get the fd "data available" notification, and create a domain event. Right? -- Hollis Blanc

Re: [Qemu-devel] Re: [libvirt] Re: [PATCH 2/3] Introduce monitor 'wait' command

On Wed, 2009-04-08 at 16:14 -0500, Anthony Liguori wrote: > Hollis Blanchard wrote: > > On Wed, 2009-04-08 at 14:35 -0500, Anthony Liguori wrote: > > > >> You're basically saying that if something isn't connected, drop them. > >> If it is connec

Re: [Qemu-devel] Re: [libvirt] Re: [PATCH 2/3] Introduce monitor 'wait' command

u care, you can attach a logging daemon that keeps the last 10 minutes worth of data... -- Hollis Blanchard IBM Linux Technology Center -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Re: [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5)

? -- Hollis Blanchard IBM Linux Technology Center -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [Libvir] big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?

hing in the kernel because userspace calls us with improper parameters, I think it goes without saying that we should fix userspace... -- Hollis Blanchard IBM Linux Technology Center -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list