From: Laine Stump <laine@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] listing "bus" option in output of "qemu -device $devname, ?"
Date: Thu, 11 Apr 2013 14:33:16 -0400 [thread overview]
Message-ID: <516701EC.8020209@redhat.com> (raw)
I was just talking to Michael Tsirkin on IRC about determining which
devices accepted a "bus" option, and asked why this option doesn't show
up in the output of "qemu -device $devname,?" (as happens for addr,
etc). He said this is an old bug, and asked that I send mail to the list
as a reminder that it should be fixed.
So here is the reminder email :-)
(note that I don't currently have any plans to use such informational
output in libvirt; mainly I was interested in seeing it when manually
running the command, as an aid to figuring out the nature of each device
and how they can be categorized.)
reply other threads:[~2013-04-11 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=516701EC.8020209@redhat.com \
--to=laine@redhat.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).