Hi,
(Sorry for the late reply!)
On (Thu) 20 Jun 2013 [10:20:01], mdroth wrote:
On Thu, Jun 20, 2013 at 10:12:30AM -0500, mdroth wrote:
On Wed, Jun 19, 2013 at 01:17:57PM +0200, Laszlo Ersek wrote:
Hello Michael,
this is with reference to
On (Wed) 19 Jun 2013 [13:17:57], Laszlo Ersek wrote:
Hello Michael,
this is with reference to
https://bugzilla.redhat.com/show_bug.cgi?id=907733.
Ever since the initial qemu-ga commit AFAICS an exception for
virtio-serial has existed, when reading EOF from the channel.
For isa-serial,
On Wed, Jun 19, 2013 at 01:17:57PM +0200, Laszlo Ersek wrote:
Hello Michael,
this is with reference to
https://bugzilla.redhat.com/show_bug.cgi?id=907733.
Ever since the initial qemu-ga commit AFAICS an exception for
virtio-serial has existed, when reading EOF from the channel.
For
On Thu, Jun 20, 2013 at 10:12:30AM -0500, mdroth wrote:
On Wed, Jun 19, 2013 at 01:17:57PM +0200, Laszlo Ersek wrote:
Hello Michael,
this is with reference to
https://bugzilla.redhat.com/show_bug.cgi?id=907733.
Ever since the initial qemu-ga commit AFAICS an exception for
On 06/20/13 15:31, Amit Shah wrote:
On (Wed) 19 Jun 2013 [13:17:57], Laszlo Ersek wrote:
In any case we'd need a way to tell host side close from port unplug.
Will POLLHUP|POLLERR help, along with error returns on read() and
write()?
I think so:
- read() == 0 -- host side disconnected,
-
Hello Michael,
this is with reference to
https://bugzilla.redhat.com/show_bug.cgi?id=907733.
Ever since the initial qemu-ga commit AFAICS an exception for
virtio-serial has existed, when reading EOF from the channel.
For isa-serial, EOF results in the client connection being closed. I
assume
