All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Neill <rn214@hermes.cam.ac.uk>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: user-net -redir working? [problem located]
Date: Tue, 22 Nov 2005 22:04:32 +0000	[thread overview]
Message-ID: <438395F0.5010000@hermes.cam.ac.uk> (raw)


> Re: User-net not working:
> 
> > Disabling the Nagle algorithm (i.e., enabling TCP_NODELAY) or typing a
> > lot of garbage just to fill the buffer with enough data can help,
> > also.
> > 
> > And IIRC, netcat has a UDP mode as well. I see no reason for this to
> > happen, but is there any chance it's using UDP by default, and you're
> > only redirecting TCP?
> > 
> > Good luck!
> 
> Thanks for your message.
> 
> I think that -redir really is broken: I've also been unsuccessful in 
> trying to make it work using an FTP server on a Windows guest, and using 
> the SSH server on a knoppix guest. Has anyone here ever had success with 
> it? It also fails on hosts with 2 different versions of Mandrake.
> 
> Anyway, I've taken your suggestion, and run both ends with ethereal. 
> Here's what I did:
> 
> 
> HOST (Linux);
>    qemu -cdrom /dev/cdrom -boot d -user-net -redir tcp:2200::22
> 
> GUEST (Knoppix):
>    Boot up, then start sshd. Verify that I can indeed do ssh
>    root@localhost, and that PermitRootLogin is yes in sshd_config.
> 
>     Then, start ethereal (on the "any" interface)
> 
> 
> HOST:
>    Start ethereal (on the "any" interface")
>    ssh -p 2200 root@localhost
> 
>   At this point, ssh just stalls. It's obviously waiting for something,
>   but not known what. I get no output at all from it.


Can you try "ssh -p 2200 root@<my IP address not localhost>

I've run into this several times dealing with the -redir
function, especially since localhost resolves as 127.0.0.1.
On my Solaris host with a linux guest, the packet arriving
showed up as 127.0.0.1, which ended up with the same
behavior as you're describing.


---------------


Dear Ben,

Good guess! That's an ingenious bit of debugging, and it now works 
perfectly. I suppose that now means 3 things need to be done:

1)Figure out *why* it doesn't work. It's definitely QEMU-specific, since 
if I run 2 separate netcat processes on the host, I have no problem. I'd 
be interested to know why this occurs. In particular, is it a problem 
with the user-net stuff on the host, or a problem with the guest?

2)Fix it...   :-)

3)Document this on the website as a known bug, so Google can find it. 
Currently, anyone using an earlier version will just think that qemu is 
broken. It hasn't worked since at least 0.6.1, although I can't tell you 
about earlier versions.

I suspect that I am not up to the task of (2), so I must defer to the 
experts...

Best wishes,

Richard

             reply	other threads:[~2005-11-22 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 22:04 Richard Neill [this message]
2005-11-23  8:33 ` [Qemu-devel] Re: user-net -redir working? [problem located][PATCH] Mark Jonckheere
2005-11-23 15:55   ` Jim C. Brown
  -- strict thread matches above, loose matches on Subject: below --
2005-11-23 16:10 [Qemu-devel] Re: user-net -redir working? [problem located] Ben Taylor

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=438395F0.5010000@hermes.cam.ac.uk \
    --to=rn214@hermes.cam.ac.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 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.