From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 18 Sep 2009 08:30:08 -0700 From: Jerome Ibanes To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <9ac57188fd3dd591041a4c7d5c5a3c56@quanstro.net> Message-ID: References: <9ac57188fd3dd591041a4c7d5c5a3c56@quanstro.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [9fans] Netbooting from Qemu Topicbox-Message-UUID: 71e53284-ead5-11e9-9d60-3106f5b1d025 As it appears, the (net)boot configuration, meaning the 'plan9.ini' located in /cfg/pxe/xxxxxxxxxxxx, where 'xxxxxxxxxxxx' 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 present, but incorrectly set, the netbooted host will prompt for the machine's hostowner's key. If this parameter is missing, the boot sequence halts. Therefore I would like to ask the 9fans community what are the best practices to host the nvram key in a diskless environment, in either a qemu virtualized machine or physical hardware. I am aware of serial Eeproms connecting to parallel ports to store the nvram data ( http://rs-rlab.narod.ru/9nvram.html ), I find it a good solution, but unfortunately, most "modern" hardware doesn't necessarly include a parallel port anymore, or even a floppy disk. 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 storage. Sincerely, Jerome