From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Libvirt <libvir-list@redhat.com>, Eric Blake <eblake@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] libvirt doesn't work with qemu 1.0
Date: Thu, 26 Jan 2012 11:55:42 +0100 [thread overview]
Message-ID: <m3ty3ibump.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4F211FE7.409@redhat.com> (Paolo Bonzini's message of "Thu, 26 Jan 2012 10:41:59 +0100")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 01/26/2012 04:55 AM, Eric Blake wrote:
>>
>> $ /usr/libexec/qemu-kvm -qmp stdio -S -display none
>> qemu-kvm: -display: invalid option
>> $ /usr/libexec/qemu-kvm -qmp stdio -S -nographic
>> chardev: opening backend "stdio" failed
>> qemu: could not open serial device 'stdio': Argument list too long
The "argument list too long" is of course random crap found errno. The
real cause is trying to create multiple stdio character devices. The
other one is the -serial stdio you get by default with -nographic and no
default monitor (-qmp suppresses that one).
Character device creation error reporting is generally atrocious. I'm
working on it.
> Have you tried -nodefaults?
That suppresses the default -serial, so it should work. I always use
it, because our defaults are a labyrinth I can do without.
next prev parent reply other threads:[~2012-01-26 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 14:21 [Qemu-devel] libvirt doesn't work with qemu 1.0 Gerd Hoffmann
2011-12-02 14:50 ` Anthony Liguori
2011-12-02 15:08 ` Jiri Denemark
2011-12-02 15:15 ` Anthony Liguori
2011-12-02 19:29 ` [Qemu-devel] [libvirt] " Eric Blake
2011-12-02 20:32 ` Anthony Liguori
2012-01-26 3:55 ` Eric Blake
2012-01-26 9:41 ` Paolo Bonzini
2012-01-26 10:55 ` Markus Armbruster [this message]
2012-01-26 12:46 ` Eric Blake
2012-01-26 13:00 ` Paolo Bonzini
2012-01-26 19:23 ` Luiz Capitulino
2011-12-02 18:53 ` Dave Allan
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=m3ty3ibump.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.