From: Avi Kivity <avi@redhat.com>
To: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
Cc: lcapitulino@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] Re: [RFC] QMP: Introduce query-netdevices documentation
Date: Sun, 06 Jun 2010 18:50:28 +0300 [thread overview]
Message-ID: <4C0BC3C4.6010207@redhat.com> (raw)
In-Reply-To: <1275660360-12137-1-git-send-email-miguel.filho@gmail.com>
On 06/04/2010 05:06 PM, Miguel Di Ciurcio Filho wrote:
> This introduces the protocol specification for querying information about
> network devices available on a VM and a new monitor command that show the same
> information.
>
> Signed-off-by: Miguel Di Ciurcio Filho<miguel.filho@gmail.com>
> ---
> qemu-monitor.hx | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 69 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-monitor.hx b/qemu-monitor.hx
> index f6a94f2..8600129 100644
> --- a/qemu-monitor.hx
> +++ b/qemu-monitor.hx
> @@ -1674,6 +1674,75 @@ show the various VLANs and the associated devices
> ETEXI
>
> STEXI
> +@item info netdevices
> +show information about network devices
> +ETEXI
> +SQMP
> +query-netdevices
> +----------------
> +
> +Each device is represented by a json-object. The returned value is a json-array
> +of all devices.
> +
> +Each json-object contain the following:
> +
> +- "device": device name (json-string)
> +- "vlan": only present if the device is attached to a VLAN (json-int)
> +- "info": json-object containing the following:
> + - "model": type of the device (json-string)
> + - Possible values: "tap", "socket", "xen", "slirp", "dump",
> + "vde", "ne2k_pci", "i82551", "i82557b",
> + "i82559er", "rtl8139", "e1000", "pcnet",
> + "virtio", "dp83932", "lan9118", "mcf_fec",
> + "xilinx-ethlite", "lance", "stellaris",
> + "smc91c111", "ne2k_isa", "mv88w8618",
> + "mipsnet", "fseth", "dp83932", "usb"
>
This casts the vlan model into concrete. I thought we wanted to move
away from it? Instead have separate entries for host and guest devices.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-06 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 14:06 [Qemu-devel] [RFC] QMP: Introduce query-netdevices documentation Miguel Di Ciurcio Filho
2010-06-06 15:50 ` Avi Kivity [this message]
2010-06-07 12:57 ` [Qemu-devel] " Miguel Di Ciurcio Filho
2010-06-07 13:39 ` Avi Kivity
2010-06-07 13:48 ` Anthony Liguori
2010-06-07 14:41 ` Miguel Di Ciurcio Filho
2010-06-07 14:48 ` Anthony Liguori
2010-06-07 19:39 ` Miguel Di Ciurcio Filho
2010-06-07 15:01 ` Markus Armbruster
2010-06-07 19:48 ` Miguel Di Ciurcio Filho
2010-06-07 15:54 ` Avi Kivity
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=4C0BC3C4.6010207@redhat.com \
--to=avi@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=miguel.filho@gmail.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).