9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Netbooting from Qemu
Date: Thu, 17 Sep 2009 19:54:36 -0400	[thread overview]
Message-ID: <9ac57188fd3dd591041a4c7d5c5a3c56@quanstro.net> (raw)
In-Reply-To: <Pine.SUN.4.58.0909171547410.8301@eskimo.com>

>   bootfile=ether0!/386/9pccpu.gz
>   bootargs=tcp!192.168.1.40!564 -D
>   fs=192.168.1.40
>   auth=192.168.1.50
>   sysname=cpu-003
>   *nomp=1
>   *debugload=1
>   *nodumpstack=1

i think that should be should be (indent for clarity)

	bootfile=ether0!$mydhcpserver!/386/9pccpu.gz
	nobootprompt=tcp

otherwise i believe you will be prompted on the
console for a root fs.

also, you would be much better off creating a ipnet
entry in ndb.  i have a dim recollection of having trouble
when this was set up incorrectly, causing cs confusion.
setting the ipnet stuff allows the fs ip addr to be
inferred.

in your case, you want entries something like this:

	ipnet=mynet ip=192.168.1.0 ipmask=/120
		fs=myfs.example.net
		ipgw=192.168.1.?
		gw=mygw.example.net
		dns=192.168.1.40
		dnsdomain=example.net
		authdom=myauthdom
		auth=myfs
		cpu=myfs

	sys=mygw ip=192.168.1.? ether=000102030405
		dom=mygw.example.net

	sys=myfs ip=192.168.1.40 ether=000102030405
		dom=myfs.example.net

	sys=cpu-003 ip=192.168.1.33 ether=000102030405
		dom=cpu-003.example.net
		bootf=/386/9pxeload

- erik



  reply	other threads:[~2009-09-17 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 23:10 Jerome Ibanes
2009-09-17 23:54 ` erik quanstrom [this message]
2009-09-18 15:30   ` Jerome Ibanes
2009-09-18 15:42     ` erik quanstrom
2009-09-18 16:09     ` Steve Simon
2009-09-18 17:55     ` Tim Newsham

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=9ac57188fd3dd591041a4c7d5c5a3c56@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).