qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] -serial stdio broken
Date: Thu, 7 Jan 2010 13:27:12 +0000	[thread overview]
Message-ID: <20100107132712.GF11507@amd.home.annexia.org> (raw)
In-Reply-To: <20100107124417.GA9028@redhat.com>

On Thu, Jan 07, 2010 at 12:44:17PM +0000, Daniel P. Berrange wrote:
> On Thu, Jan 07, 2010 at 06:34:13AM -0600, Anthony Liguori wrote:
> > On 01/07/2010 05:55 AM, Richard W.M. Jones wrote:
> > >On Sun, Dec 13, 2009 at 08:24:54AM +0000, Blue Swirl wrote:
> > >   
> > >>I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or
> > >>998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all
> > >>targets:
> > >>qemu -serial stdio -monitor stdio
> > >>chardev: opening backend "stdio" failed
> > >>qemu: could not open serial device 'stdio': No such file or directory
> > >>     
> > >-serial stdio on its own is broken for me (qemu from git).  The error
> > >is a little bit different, so I don't think this is the same bug:
> > >
> > >   chardev: opening backend "stdio" failed
> > >   qemu: could not open serial device 'stdio': Invalid argument
> > >
> > >The full command line is:
> > >
> > >$qemudir/x86_64-softmmu/qemu-system-x86_64 \
> > >     -L $qemudir/pc-bios \
> > >     -drive file=/tmp/test.img,cache=off,if=ide \
> > >     -m 500 \
> > >     -no-reboot \
> > >     -nographic \
> > >     -serial stdio \
> > >   
> > 
> > This is redundant.  -nographic implies -serial stdio.
> 
> NB, QEMU 0.12 introduces a new flag '-nodefaults' that can be used to
> get rid of this imlied 'serial stdio', and all other implied devices.
> It is well worth using this new -nodefaults flag if you're managing
> qemu from an app to avoid these surprises
> 
> eg this should work as you'd expect it
> 
>   qemu -nodefaults -nographic -serial stdio

I think this is probably the way to go then.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

      parent reply	other threads:[~2010-01-07 13:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  8:24 [Qemu-devel] -serial stdio broken Blue Swirl
2009-12-13  9:38 ` [Qemu-devel] " Blue Swirl
2009-12-14 10:55   ` Gerd Hoffmann
2009-12-14 16:50     ` Blue Swirl
2009-12-14 17:12       ` Gerd Hoffmann
2010-01-07 11:55 ` [Qemu-devel] " Richard W.M. Jones
2010-01-07 12:10   ` Richard W.M. Jones
2010-01-07 12:32     ` Gerd Hoffmann
2010-01-07 13:25       ` Richard W.M. Jones
2010-01-07 16:01         ` Anthony Liguori
2010-01-07 12:35     ` Anthony Liguori
2010-01-07 12:34   ` Anthony Liguori
2010-01-07 12:44     ` Daniel P. Berrange
2010-01-07 13:23       ` Anthony Liguori
2010-01-07 13:27       ` Richard W.M. Jones [this message]

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=20100107132712.GF11507@amd.home.annexia.org \
    --to=rjones@redhat.com \
    --cc=berrange@redhat.com \
    --cc=blauwirbel@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).