From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc
Date: Sun, 31 Jan 2016 15:19:40 +0000 [thread overview]
Message-ID: <56AE260C.9020508@ilande.co.uk> (raw)
Hi Daniel,
Commit d0d7708ba29cbcc343364a46bff981e0ff88366f "qemu-char: add logfile
facility to all chardev backends" appears to be causing problems with
the monitor and stdin/stdout on both qemu-system-sparc/qemu-system-ppc here.
On current git master I see the following behaviour changes when
launching qemu-system-ppc/qemu-system-sparc directly from the command
line with no parameters:
- Serial port output is now also written to stdout
- The monitor output also appears on stdout by default, rather than
being enabled with CTRL-A-c. However if I enter this sequence manually
on stdin then I am unable to enter or interact with the monitor.
- If I use the gtk interface to switch to the monitor terminal and
attempt to type, I get multiple copies of each letter echoed back in the
graphical terminal
Are there other changes that need to be made to these targets in order
for the functionality to work as before?
Many thanks,
Mark.
next reply other threads:[~2016-01-31 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 15:19 Mark Cave-Ayland [this message]
2016-01-31 15:34 ` [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc Peter Maydell
2016-01-31 15:54 ` Mark Cave-Ayland
2016-01-31 17:19 ` Paolo Bonzini
2016-01-31 17:54 ` Peter Maydell
2016-01-31 21:57 ` Paolo Bonzini
2016-02-02 7:47 ` Mark Cave-Ayland
2016-02-08 9:08 ` Paolo Bonzini
2016-02-08 21:44 ` Mark Cave-Ayland
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=56AE260C.9020508@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--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).