qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Martin <jmartin@notamusica.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu -serial pty bug and serial/slirp considerations
Date: Tue, 21 Sep 2004 21:47:11 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0409212138150.3700@hatatitla.NotaMusica.com> (raw)

Hi,

when I run qemu -serial -pty I get output like:
	char device redirected to @¡<@ T<@ðy.@u

This is because vl.c calls openpty() as follows:
	    if (openpty(&master_fd, &slave_fd, slave_name, NULL, NULL) < 0)
while in slirp/misc.c openpty() expects only two parameters (current CVS).

Well, by looking in /proc/<pid>/fd I can find out which pty qemu opened so
there's no real harm done.



I just successfully attached a pppd to the qemu pty and finally got a
stable network connection working in my OS/2 Warp 4 guest. I should have
thought about this before rather than trying to get NE2000 and PCNET to
work in OS/2.

Thinking on this line, it would be really neat to be able to attach the
qemu-internal slirp to the virtual com port so any guest could access
SLIP/ppp through the serial port (ppp needs root permissions and I haven't
figured out how to run slirp proper on a pty - any hints?).

	Johannes

                 reply	other threads:[~2004-09-21 19:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.56.0409212138150.3700@hatatitla.NotaMusica.com \
    --to=jmartin@notamusica.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).