[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-tech-net
Subject:    xen boot parameter for network boot
From:       Christoph Egger <Christoph_Egger () gmx ! de>
Date:       2008-10-24 20:41:46
Message-ID: 4902330A.3070808 () gmx ! de
[Download RAW message or body]


Hi!

In order to boot a netbsd dom0 from network with root on nfs,
currently I have to pass the following parameters to the dom0:

bootdev=ex0 ip=10.2.0.12:10.2.0.14:10.2.0.254:10.2.0.0:10.2.0.12:eth0
nfsroot=10.2.0.14:/nfsroot/netbsd-amd64-machine1-cegger

The only one documentation for the ip parameter I found so far is the
source file sys/arch/xen/xen/xen_machdep.c, function xen_parse_cmdline().

The disadvantage I am really suffering on is, I need one boot menu entry
for each test machine and for each NetBSD version (i386, amd64,
older/newer snapshots).


This patch improves the situation:

http://www.netbsd.org/~cegger/nfs_boot.diff


The patch allows me to give partial information and the new
boot code retrieves missing information via the next nfs boot method
until all required information are there.

Example 1:

bootdev=ex0 ip=0:10.2.0.14:0:0:0:eth0
nfsroot=10.2.0.14:/nfsroot/netbsd-amd64-machine1-cegger

Example 2:

bootdev=ex0 ip=dhcp nfsroot=10.2.0.14:/nfsroot/netbsd-amd64-machine1-cegger

Example 3:

bootdev=ex0 nfsroot=10.2.0.14:/nfsroot/netbsd-amd64-machine1-cegger


The patch allows me to have only *one* boot menu entry for each
NetBSD version independent how many different test machines I have.

The original configuration still works.

Any comments ?

Christoph

[prev in list] [next in list] [prev in thread] [next in thread]