From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Programmingkid <programmingkidx@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths
Date: Fri, 11 Sep 2015 06:46:31 -0600 [thread overview]
Message-ID: <55F2CD27.9000407@redhat.com> (raw)
In-Reply-To: <1441974836-17476-1-git-send-email-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On 09/11/2015 06:33 AM, Daniel P. Berrange wrote:
> Currently device_del requires that the client provide the
> device short ID. device_add allows devices may be created
> without giving an ID, at which point there is no way to
> delete them with device_del. The QOM object path, however,
> provides an alternative way to identify the devices.
>
> Allowing device_del to accept an object path ensures all
> devices are deletable regardless of whether they have an
> ID.
>
> (qemu) device_add usb-mouse
> (qemu) qom-list /machine/peripheral-anon
> device[0] (child<usb-mouse>)
> type (string)
> (qemu) device_del /machine/peripheral-anon/device[0]
>
> Devices are required to be marked as hotpluggable
> otherwise an error is raised
>
> (qemu) device_del /machine/unattached/device[4]
> Device 'PIIX3' does not support hotplugging
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-09-11 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 12:33 [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths Daniel P. Berrange
2015-09-11 12:46 ` Eric Blake [this message]
2015-09-14 15:53 ` Markus Armbruster
2015-09-14 16:17 ` Programmingkid
2015-09-14 16:41 ` Eric Blake
2015-09-14 16:49 ` Programmingkid
2015-09-14 17:08 ` Eric Blake
2015-09-14 16:43 ` Markus Armbruster
2015-09-14 16:54 ` Programmingkid
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=55F2CD27.9000407@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=programmingkidx@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).