qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [CFR 8/10] device_add command


From: Anthony Liguori
Subject: Re: [Qemu-devel] [CFR 8/10] device_add command
Date: Tue, 15 Jun 2010 11:49:03 -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 11:30 AM, Anthony Liguori wrote:
device_add
----------

Add a device.

Arguments:

- "driver": the name of the new device's driver (json-string)

What class of name is this? I believe this is a qdev name but the example is misleading because someone could reasonable do { "driver": "virtio", "id": "net1"}

- "bus": the device's parent bus (device tree path, json-string, optional)
- "id": the device's ID, must be unique (json-string)
- device properties

I think we need to document all of the supported devices and their properties as part of the spec.

What happens if we cannot add the device? How does one use this for hot add?

Is the device available within the guest immediately after the device_add operation completes?

Regards,

Anthony Liguori

Example:

->  { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } 
}
<- { "return": {} }

Notes:

(1) For detailed information about this command, please refer to the
     'docs/qdev-device-use.txt' file.

(2) It's possible to list device properties by running QEMU with the
     "-device DEVICE,\?" command-line argument, where DEVICE is the device's 
name





reply via email to

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