store located on kfs. Please share with the list if you are aware, or use
a different method to store your nvram data, either in virtualized
machines or physical hardware. Preferably without the use of disk/floppy
storage.
If its an emulated environment, just put it on an emulated disk.
Its real
I would have thought a small USB stick would be the way to go,
My latest motherboard even had one USB port inside the case
for just this kind of thing.
-Steve
> I assume (perhaps incorrectly) that the netbooted host can not use a nvram
> store located on kfs. Please share with the list if you are aware, or use
> a different method to store your nvram data, either in virtualized
> machines or physical hardware. Preferably without the use of disk/floppy
>
As it appears, the (net)boot configuration, meaning the 'plan9.ini'
located in /cfg/pxe/, where '' is the netbooted
host ethernet address, was missing nvram parameters, preventing the cpu
kernel (9pccpu) to proceed with the boot sequence.
If this parameter (nvram or nvr) is
> 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
Hi,
I am (net)booting a Qemu instance from a Plan 9 fileserver named
colossus(192.168.1.40) running cwfs, an authserver, named
cerberus(192.168.1.50) is also present in the same domain.
The client is named cpu-003(192.168.1.33), it retrieves, via dhcp its
plan9.ini, which is as such:
bootfile=
