From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9ac57188fd3dd591041a4c7d5c5a3c56@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 17 Sep 2009 19:54:36 -0400
To: 9fans@9fans.net
In-Reply-To: <Pine.SUN.4.58.0909171547410.8301@eskimo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Netbooting from Qemu
Topicbox-Message-UUID: 71c73068-ead5-11e9-9d60-3106f5b1d025

>   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