All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: -serial stdio broken
Date: Mon, 14 Dec 2009 11:55:03 +0100	[thread overview]
Message-ID: <4B261987.6080807@redhat.com> (raw)
In-Reply-To: <f43fc5580912130138h246ced19i6d248e4ab6251b4f@mail.gmail.com>

On 12/13/09 10:38, Blue Swirl wrote:
> On Sun, Dec 13, 2009 at 8:24 AM, Blue Swirl<blauwirbel@gmail.com>  wrote:
>> I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or
>> 998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all
>> targets:
>> qemu -serial stdio -monitor stdio

Oh.  It is actually used on the command line.  Hmm.

First, you can use '-serial mon:stdio' instead.

Second, with 'qemu -nographic' you don't need to specify this at all 
because that is the default.

What is gone now is the automagic conversion of '-serial stdio -monitor 
stdio' into '-serial mon:stdio' because I didn't expect people actually 
using that on the command line (see commit message).  Also this kind of 
post-processing is pretty horrible thing for the command line parser 
code.  Thus I would pretty much prefer to not re-introduce this ...

Can you live with one of the alternatives outlined above?

cheers,
   Gerd

  reply	other threads:[~2009-12-14 10:55 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 [this message]
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

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=4B261987.6080807@redhat.com \
    --to=kraxel@redhat.com \
    --cc=blauwirbel@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 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.