On (Thu) 29 May 2014 [21:36:39], Laszlo Ersek wrote:
In this series I try to implement the ideas that (I believe) were
suggested by Gerd and Amit in
https://bugzilla.redhat.com/show_bug.cgi?id=1080376.
When the guest agent exits or dies (disconnects from the virtio-serial
port), the backend
In this series I try to implement the ideas that (I believe) were
suggested by Gerd and Amit in
https://bugzilla.redhat.com/show_bug.cgi?id=1080376.
When the guest agent exits or dies (disconnects from the virtio-serial
port), the backend (eg. a host-side unix domain socket) doesn't (in
general,
On 05/29/2014 01:36 PM, Laszlo Ersek wrote:
In this series I try to implement the ideas that (I believe) were
suggested by Gerd and Amit in
https://bugzilla.redhat.com/show_bug.cgi?id=1080376.
When the guest agent exits or dies (disconnects from the virtio-serial
port), the backend (eg. a
On 05/29/14 21:47, Eric Blake wrote:
virsh qemu-monitor-event $dom serport --no-case --regex --pretty --loop
to set up a listening loop that will fire on all case-insensitive events
matching the regex serport (basically, the two events added in this
patch) that occur on $dom, until you get
On 05/29/2014 01:36 PM, Laszlo Ersek wrote:
In this series I try to implement the ideas that (I believe) were
suggested by Gerd and Amit in
https://bugzilla.redhat.com/show_bug.cgi?id=1080376.
When the guest agent exits or dies (disconnects from the virtio-serial
port), the backend (eg. a
On 05/29/14 22:24, Eric Blake wrote:
On 05/29/2014 01:36 PM, Laszlo Ersek wrote:
In this series I try to implement the ideas that (I believe) were
suggested by Gerd and Amit in
https://bugzilla.redhat.com/show_bug.cgi?id=1080376.
When the guest agent exits or dies (disconnects from the
On 05/29/2014 02:54 PM, Laszlo Ersek wrote:
Thinking about it a bit more, would it help to make the frontend_open a
tri-state? It would be nice to know the difference between a guest that
has no idea how to use the channel (has never opened it in the past;
possibly because we're still too
