From: andrzej zaborowski <balrogg@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] "qemu -device ?" segfaults
Date: Thu, 23 Feb 2012 09:25:53 +0100 [thread overview]
Message-ID: <CAOq732JEoXT7HAXXSC7i9MMaFs3PtBp5MhgA0wiSnmBQgdLTUA@mail.gmail.com> (raw)
In-Reply-To: <4F45F6C7.6010000@redhat.com>
On 23 February 2012 09:20, Gerd Hoffmann <kraxel@redhat.com> wrote:
> $subject says all, which pretty much breaks libvirt-managed qemu ...
Also "device_add nonexistent-device" in the monitor gives a rather
unhelpful message:
Parameter 'driver' expects device type
Cheers
next prev parent reply other threads:[~2012-02-23 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:20 [Qemu-devel] "qemu -device ?" segfaults Gerd Hoffmann
2012-02-23 8:23 ` Gerd Hoffmann
2012-02-23 8:23 ` Peter Maydell
2012-02-23 8:52 ` Gerd Hoffmann
2012-02-23 8:25 ` andrzej zaborowski [this message]
2012-02-23 8:48 ` Markus Armbruster
2012-02-23 8:57 ` andrzej zaborowski
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=CAOq732JEoXT7HAXXSC7i9MMaFs3PtBp5MhgA0wiSnmBQgdLTUA@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=kraxel@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).