9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] port forwarding
Date: Thu, 12 Jun 2014 08:53:40 +0100	[thread overview]
Message-ID: <CAOw7k5gxaO+Bb+4MHpUi4ZwN5P8TxNjV-q6_wnKCq-Fk-NytBg@mail.gmail.com> (raw)
In-Reply-To: <20140612072922.GD14836@iota.offblast.org>

[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]

>
> The qemu instance needs to boot from the auth+fs server.


Note that qemu instance loads from an elf file, so it doesn't need to PXE
boot, which might make it a little simpler.
"Boot from" here means "root from ...".


On 12 June 2014 08:29, Nick Owens <mischief@9.offblast.org> wrote:

> yan,
>
> you need to set up some kind of bridge. there's a few options. in my
> setup, i use libvirt. with libvirt, i configured one vm with two NICs,
> one for the 'internet' and one for a private network between my
> cpu/auth/fs and a pxe booted vm for testing. i put ether0 on /net
> (private lan) and ether1 on /net.alt. in this way, i can pxe boot a vm
> from the first one, and it has internet access by importing /net.alt.
>
> in this way, i can change code, recompile on vm 1, and then boot vm 2
> over pxe to test, so i don't lose any state in vm 1 through reboots or
> crashes.
>
> http://www.linux-kvm.org/page/Networking describes various ways to
> configure networking in kvm.
> libvirt removes some of the manual work here required for configuring
> the bridges and interfaces of the vms.
>
> it's not very coherent but http://9.offblast.org/9front/guide/PXE_boot
> talks a little bit about my setup, except in the doc i say that i used
> /net for the NAT side and /net.alt for the private side. now i use the
> opposite.
>
> good luck.
>
> On Thu, Jun 12, 2014 at 12:52:33AM -0400, yan cui wrote:
> > Hi all,
> >
> >     I run into a situation that may need to setup the port forwarding
> rule,
> > but not quite sure. Hope you guys can provide some suggestions. Thanks in
> > advance!
> >
> > Basically, I have a virtual machine (KVM) working as plan9's fs+auth
> > server.
> > The auth+fs server listens the port 564 and uses NAT (network address
> > translation) to connect to the Internet.
> >
> > The virtual machine runs on a Linux box. On the same Linux machine,
> > I use qemu to execute an enhanced plan9 cpu server (with new features
> > included). The qemu instance needs to boot from the auth+fs server.
> > My question is, to make the boot successful, do I need to set any port
> > forwarding rules? If so, how to do that?
> >
> >
> > --
> > Think big; Dream impossible; Make it happen.
>

[-- Attachment #2: Type: text/html, Size: 3251 bytes --]

  reply	other threads:[~2014-06-12  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  4:52 yan cui
2014-06-12  7:29 ` Nick Owens
2014-06-12  7:53   ` Charles Forsyth [this message]
2014-06-12  9:56     ` Aram Hăvărneanu

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=CAOw7k5gxaO+Bb+4MHpUi4ZwN5P8TxNjV-q6_wnKCq-Fk-NytBg@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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).