From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36593 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOwat-0001W3-Tc for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:40:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OOwa6-00014u-D5 for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:39:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1338) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OOwa6-00014k-5j for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:39:18 -0400 Date: Wed, 16 Jun 2010 14:39:08 -0300 From: Luiz Capitulino Message-ID: <20100616143908.7ba3e92f@redhat.com> In-Reply-To: <1276205825-1922-3-git-send-email-miguel.filho@gmail.com> References: <1276205825-1922-1-git-send-email-miguel.filho@gmail.com> <1276205825-1922-3-git-send-email-miguel.filho@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 2/8] QMP: Introduce the documentation for query-netdev and info netdev List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Miguel Di Ciurcio Filho Cc: avi@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com On Thu, 10 Jun 2010 18:36:59 -0300 Miguel Di Ciurcio Filho wrote: > These commands show the information about active backend network devices. > > Signed-off-by: Miguel Di Ciurcio Filho > --- > qemu-monitor.hx | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 53 insertions(+), 0 deletions(-) > > diff --git a/qemu-monitor.hx b/qemu-monitor.hx > index f6a94f2..14a0ba1 100644 > --- a/qemu-monitor.hx > +++ b/qemu-monitor.hx > @@ -1674,6 +1674,59 @@ show the various VLANs and the associated devices > ETEXI > > STEXI > +@item info netdev > +show information about the current backend network devices > +ETEXI > +SQMP > +query-netdev > +---------------- > + > +Each device is represented by a json-object. The returned value is a json-array > +of all devices. > + > +Each json-object contain the following: > + > +- "id": the device's ID, must be unique (json-string) > +- "vlan": QEMU's internal vlan identification. Only present if the device is > + attached to a VLAN (json-int, optional) > +- "peer": ID of the frontend device when on a 1:1 relationship (json-string, > + optional) 'type' is missing. > +- "info": json-object containing the configuration information about the device. We need a list of all backends (maybe in 'type') and then we need to list all possible cases for 'info'. I have some other comments, otherwise looks good.