qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Re: [CFR 9/10] device_del command


From: Anthony Liguori
Subject: Re: [Qemu-devel] Re: [CFR 9/10] device_del command
Date: Tue, 15 Jun 2010 16:14:22 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b1 Thunderbird/3.0.4

On 06/15/2010 03:48 PM, Miguel Di Ciurcio Filho wrote:
On Tue, Jun 15, 2010 at 1:59 PM, Jan Kiszka<address@hidden>  wrote:
Anthony Liguori wrote:
device_del
----------

Remove a device.

Arguments:

- "id": the device's ID (json-string)
"id" should become "device" (I hope to send the corresponding patches
this night). The idea is to not only allow global device IDs but also
qtree paths here.

Now I'm confused. On a previous email when discussing about
query-netdev, I initially proposed this[1]:

->  { "execute": "query-netdev" }
<- {
       "return": [
          {
             "device": "tap.0",
             "vlan": 0,
             "info": {
                "script": "/etc/qemu-ifup",
                "downscript": "/etc/qemu-ifdown",
                "ifname": "tap0",
                "model": "tap"
             },
          },

And latter on Anthony suggested to replace "device" by "id" [2].

So my doubt is: we should identify guest/frontend devices in QMP using
the word "device" instead of "id" and identify backend devices by
using the word "id"?

id.

What Jan is referring to is the qdev device path verses the qdev id. netdev objects are not qdev devices, they are just QemuOpts. In netdev parlance, the unique identifier is called the 'id'.

Regards,

Anthony Liguori

Regards,

Miguel

[1] http://lists.gnu.org/archive/html/qemu-devel/2010-06/msg00619.html
[2] http://lists.gnu.org/archive/html/qemu-devel/2010-06/msg00943.html




reply via email to

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