On Fri, Nov 11, 2016 at 10:33:11 +0000, Daniel Berrange wrote:
On Fri, Nov 11, 2016 at 11:27:07AM +0100, Peter Krempa wrote:
> On Fri, Nov 11, 2016 at 10:18:00 +0000, Daniel Berrange wrote:
> > On Fri, Nov 11, 2016 at 11:13:19AM +0100, Peter Krempa wrote:
> > > On Mon, Nov 07, 2016 at 15:48:35 -0500, Matt Broadstone wrote:
> > > > Presently domain events are emitted for the "agent
lifecycle" which
> > > > is a specialization on virtio-serial events specific to the channel
> > > > named "org.qemu.guest_agent.0". This patch adds a generic
event for
> > > > "channel lifecycles", which emit state change events for
all
> > > > attached channels.
> > > > ---
>
> [...]
These events are not solely useful for knowing when to connect to
the
channel. An application which relies on the QEMU guest agent because
of the libvirt API calls it makes, may wish to know when the guest
agent is running, so it can avoid making libvirt APIs that use it.
eg, the app can disable the ability to quiesce filesystems until it
sees the event that the agent is running.
So I don't really see the guest agent as so special that we must not
allow these events to be seen by apps - it just creates extra work
for apps to force them to pointlessly register two event callbacks.
My point was that the guest agent may still be connected but
disfunctional from libvirt's point of view. The Agent lifecycle callback
should report this, while the channel callback should not.
Such apps will need two callbacks anyways.