On Mon, Nov 07, 2016 at 03:05:24PM +0100, Peter Krempa wrote:
> On Mon, Nov 07, 2016 at 08:56:58 -0500, Matt Broadstone wrote:
> > On Mon, Nov 7, 2016 at 8:52 AM, Matt Broadstone wrote:
> > > On Mon, Nov 7, 2016 at 8:35 AM, Peter Krempa wrote:
> > >> On
On Mon, Nov 07, 2016 at 08:56:58 -0500, Matt Broadstone wrote:
> On Mon, Nov 7, 2016 at 8:52 AM, Matt Broadstone wrote:
> > On Mon, Nov 7, 2016 at 8:35 AM, Peter Krempa wrote:
> >> On Mon, Nov 07, 2016 at 13:31:30 +, Daniel Berrange wrote:
> >>> On
On Mon, Nov 7, 2016 at 8:52 AM, Matt Broadstone wrote:
> On Mon, Nov 7, 2016 at 8:35 AM, Peter Krempa wrote:
>> On Mon, Nov 07, 2016 at 13:31:30 +, Daniel Berrange wrote:
>>> On Mon, Nov 07, 2016 at 08:22:59AM -0500, Matt Broadstone wrote:
>>> > Hi,
On Mon, Nov 7, 2016 at 8:35 AM, Peter Krempa wrote:
> On Mon, Nov 07, 2016 at 13:31:30 +, Daniel Berrange wrote:
>> On Mon, Nov 07, 2016 at 08:22:59AM -0500, Matt Broadstone wrote:
>> > Hi,
>> >
>> > I was in the process of implementing a custom qemu agent which
>> >
On Mon, Nov 07, 2016 at 13:31:30 +, Daniel Berrange wrote:
> On Mon, Nov 07, 2016 at 08:22:59AM -0500, Matt Broadstone wrote:
> > Hi,
> >
> > I was in the process of implementing a custom qemu agent which
> > communicates over virtio-serial channels, when I noticed that the only
> > way to
On Mon, Nov 07, 2016 at 08:22:59AM -0500, Matt Broadstone wrote:
> Hi,
>
> I was in the process of implementing a custom qemu agent which
> communicates over virtio-serial channels, when I noticed that the only
> way to receive channel state change notifications was to poll the
> domstatus XML
Hi,
I was in the process of implementing a custom qemu agent which
communicates over virtio-serial channels, when I noticed that the only
way to receive channel state change notifications was to poll the
domstatus XML file. There does seem to be code in libvirt to monitor
for serial change events