From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting a terminal in qemu
Date: Tue, 27 Feb 2007 21:12:21 +0000 [thread overview]
Message-ID: <560951776189bde592374dfc751a0ab6@quintile.net> (raw)
In-Reply-To: <7d3530220702271130w3b4dac5fld4a48f8cc5626093@mail.gmail.com>
I don't know how you would use qemu to netboot plan9 as the server
uses the ethernet address of the client to decide who it is and which
kernel it give it. As this MAC is also assigned to the host machine
then things could get confused, perhaps there is some way of virtualising
MACs?
The cleanst way to boot a terminal is PXE as this means it can be
diskless. Failing this you can boot 9load locally, which will use
DHCP to get an IP address and the name of the kernel to fetch.
Finally you can boot moth 9load and the kernel from the local disk but
fetch your filesystem root from the remote server.
The only difference between these options is the extra hassle required to
keep the terminal's kernel up to date.
To boot from the network you will probably need to put some more detail into
/lib/ndb/local. if you can go the PXE route then put its plan9.ini /cfg/pxe/xxxxxxx
where xxxxxx is the MAC address of the terminal in lower case hex.
here is an example, though is relates to native plan9 rather than
qemu, but hopefully the recipe will be similar.
My file/auth/cpu server is felix, the terminal is glass
contents of /cfg/pxe/0002b31af559
bootfile=ether0!felix!/386/9pc
bootargs=tcp
nobootprompt=tcp
vgasize=1024x768x8
monitor=xga
mouseport=ps2
ether0=type=i82557 media=100BASE-FX
from /lib/ndb/local
sys=brick ether=0002b31af559
ip=192.168.0.7
bootf=/386/9pxeload
ipnet=myhome ip=192.168.0.0 ipmask=255.255.255.0
ipgw=192.168.0.1
dns=194.168.4.100 dns=194.168.8.100
dnsdomain=quintile.net
nntp=news.myisp.com
smtp=smtp.myisp.com
ntp=gb.public.ntp.get-time.net
authdom=home.quintile.net
auth=felix
cpu=felix
fs=felix
-Steve
next prev parent reply other threads:[~2007-02-27 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 19:30 John Floren
2007-02-27 21:12 ` Steve Simon [this message]
2007-02-27 21:09 ` William Josephson
2007-02-27 22:40 ` [9fans] " John Floren
2007-02-27 23:24 ` Russ Cox
2007-02-28 19:10 ` ron minnich
2007-02-28 19:34 ` Armando Camarero
2007-02-28 19:51 ` Gabriel Diaz
2007-03-01 3:11 ` erik quanstrom
2007-03-01 13:15 ` Armando Camarero
2007-02-28 20:13 ` Bakul Shah
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=560951776189bde592374dfc751a0ab6@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/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).