qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [RFC] QMP: Introduce query-netdevices documentation


From: Avi Kivity
Subject: [Qemu-devel] Re: [RFC] QMP: Introduce query-netdevices documentation
Date: Sun, 06 Jun 2010 18:50:28 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4

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<address@hidden>
---
  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
address@hidden 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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]