From: "Alexandre Leclerc" <alexandre.leclerc@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Using QEMU as a terminal server?
Date: Fri, 12 Jan 2007 16:12:51 -0500 [thread overview]
Message-ID: <1dc7f0e30701121312j2f7a291ah99584dd0ff0a4d2a@mail.gmail.com> (raw)
In-Reply-To: <45A7A25C.4020103@eridani.co.uk>
Michael,
Thank you for your help. Now I know it is possible. I'll try to figure
all that out. If you know any links on the web that could help me on
some specific points, I'll be glad to have a look at them.
Best regards.
2007/1/12, Michael McConnell <soruk@eridani.co.uk>:
> Alexandre Leclerc wrote:
> > Hi all,
> >
> > I was thinking to something weird, but I don't know if it is totally
> > doable. So I ask your expertise. (Being under Linux to use W2K
> > images.)
> >
> > - ssh login.
> > - then the login script launch a qemu session without the X session
> > (running without visual).
> > - there would be UltraVNC server inside the OS
> > - find a way to catch the nat ip address of this new qemu session
> > - trhu the ssh tunel, connect UltraVNC viewer to server.
> >
> > Here we go I have a nive 'Terminal Server' connection.
> >
> > Ok, if the ssh thing is not working, or simply, let us remove this
> > aspect; would such a thing be possible?
> >
> > Having something like that would be amasing because then doing
> > windows-like terminal server on linux becomes possible. You map the
> > sessions in read-only to a master image file and there you go.
>
> I do something very similar.
>
> My localnet uses IPs in 192.168.a.0/24, and my QEMU sessions operate on
> separate 192.168.b.x/30 subnets, and for my Win2000 QEMU session I have
> ipchains NATing outbound connections and transparently forwarding a
> 192.168.a.y address that is aliased on the host's eth0 (the host handles
> 192.168.a.z as normal) to the 192.168.b.x/30 address used within QEMU. I
> then just open a VNC connection to 192.168.a.y port 5900, and it all
> works fine.
>
> This forwarding means my net-facing box which handles inbound SSH from
> the internet can "see" the QEMU virtual machine without requiring a
> second level of port-forwarding.
>
> My ssh looks something like this, from the outside world:
>
> ssh -L5944:192.168.96.y:5900 -C username@hostname
>
> The -C compresses, and despite VNC doing a lot of compression on its
> own, this does help, especially on low-bandwidth connections (e.g.
> dial-up, GPRS)
>
> If you want to use user-mode networking instead of the tunnelling
> device, use the "-redir tcp:5900::5900" option for QEMU, then the host's
> port 5900 will be forwarded into the QEMU VNC server.
>
> Hope that's of some help.
>
> --
> -- Michael "Soruk" McConnell
> Eridani Star System
>
> MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
> Mail Me Anywhere - http://www.MailMeAnywhere.com/ - Mobile email
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Alexandre Leclerc
prev parent reply other threads:[~2007-01-12 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 14:33 [Qemu-devel] Using QEMU as a terminal server? Alexandre Leclerc
2007-01-12 14:59 ` Michael McConnell
2007-01-12 21:12 ` Alexandre Leclerc [this message]
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=1dc7f0e30701121312j2f7a291ah99584dd0ff0a4d2a@mail.gmail.com \
--to=alexandre.leclerc@gmail.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).