From: Amit Shah <amit.shah@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: mprivozn@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] help libvirt know what's up with qga
Date: Fri, 6 Jun 2014 15:13:05 +0530 [thread overview]
Message-ID: <20140606094305.GA6708@grmbl.mre> (raw)
In-Reply-To: <1401392201-29988-1-git-send-email-lersek@redhat.com>
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 (eg. a host-side unix domain socket) doesn't (in
> general, can't) reflect it. This lack of info tends to trip up libvirt
> in some cases, waiting indefinitely for an agent that doesn't exist.
>
> The series adds two monitor events that report about virtio-serial ports
> being opened and closed (for online notification), and extends the
> "query-chardev" QMP command's return type with a "frontend_open" bool
> (for querying at late libvirt startup).
>
> Admittedly, these two don't report on the same level (frontend vs.
> backend), but the association is under libvirt's control, so it should
> be fine, and it helps keep the series non-intrusive. (Also known as, "I
> have a fleeting chance implementing it, having authored neither chardev
> nor virtio-serial".)
Hey, that's alright :-)
I don't have a problem with the series, and please don't let me block
it -- I already see you and Eric had a nice discussion, and I don't
feel strongly about anything there -- so for things where you're
waiting on me, please pick what both of you think is best.
Thanks,
Amit
next parent reply other threads:[~2014-06-06 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401392201-29988-1-git-send-email-lersek@redhat.com>
2014-06-06 9:43 ` Amit Shah [this message]
[not found] ` <1401392201-29988-3-git-send-email-lersek@redhat.com>
[not found] ` <538794A9.1000906@redhat.com>
[not found] ` <53879BDB.8050403@redhat.com>
[not found] ` <5387A118.5090304@redhat.com>
2014-06-24 14:21 ` [Qemu-devel] [PATCH 2/2] char: report frontend open/closed state in 'query-chardev' Laszlo Ersek
2014-06-24 14:36 ` Eric Blake
2014-06-25 13:02 ` Luiz Capitulino
2014-06-25 13:14 ` Eric Blake
2014-06-25 13:16 ` Luiz Capitulino
2014-06-25 13:25 ` Laszlo Ersek
2014-06-25 13:30 ` Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140606094305.GA6708@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).