From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] How to create multiplexed chardevs?
Date: Mon, 22 Mar 2010 17:39:48 +0100 [thread overview]
Message-ID: <4BA79D54.3060300@siemens.com> (raw)
Hi Gerd,
I think you mostly worked on this:
How to specify -serial mon:stdio using the new syntax? I just ran into
the problem having to define a serial port via -device isa-serial but
wanting its terminal multiplexed with a monitor. -chardev mon:stdio is
not understood.
BTW, there is are thousand ways of shooting yourself into the foot (up
to crashing qemu) by accidentally combining old and new-style options. I
think we should catch and forbid any mixture instead of generating error
messages like this:
qemu-system-x86_64 -mon monitor -chardev stdio,id=monitor -monitor vc
tried to create id "monitor" twice for "chardev"
parse error: vc
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next reply other threads:[~2010-03-22 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 16:39 Jan Kiszka [this message]
2010-03-22 17:06 ` [Qemu-devel] Re: How to create multiplexed chardevs? Gerd Hoffmann
2010-03-22 17:15 ` Jan Kiszka
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=4BA79D54.3060300@siemens.com \
--to=jan.kiszka@siemens.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 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.