From: Anthony Liguori <anthony@codemonkey.ws>
To: "Richard W.M. Jones" <rjones@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, 07 Jan 2010 10:01:11 -0600 [thread overview]
Message-ID: <4B460547.6050306@codemonkey.ws> (raw)
In-Reply-To: <20100107132536.GE11507@amd.home.annexia.org>
On 01/07/2010 07:25 AM, Richard W.M. Jones wrote:
> On Thu, Jan 07, 2010 at 01:32:09PM +0100, Gerd Hoffmann wrote:
>
>> Hi,
>>
>>
>>> So what seems to be happening here is there is an implicit monitor
>>> being set up which grabs stdio. Because:
>>>
>>> #define STDIO_MAX_CLIENTS 1
>>>
>>> my own -serial stdio option subsequently fails. This is a regression
>>> over previous behaviour. I didn't specify a monitor device, because I
>>> don't want one, and previous versions of qemu didn't give me one in
>>> nographic mode.
>>>
>> They gave you a monitor too. Try typing 'Ctrl-A c' on stdio, and you'll
>> see. qemu tries to be more clever than you. Which sucks IMHO. But
>> getting rid of that without adding regressions seems to be really hard
>> ...
>>
>> Easiest way to workaround this is to simply not specify '-serial stdio'.
>> It is the default anyway for -nographic, so you don't have to.
>>
> I want to see the output of the serial port on stdio though. I don't
> care at all about the monitor.
>
-nographic gives you that.
nographic is a terrible name. It really is, use this mode if you want
to run something and only interact with it through the serial console.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-07 16:01 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 [this message]
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=4B460547.6050306@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).