Re: [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not

[Mike <mc-al34luc@sbcglobal.net>]

Richard Miller wrote:
> Try deleting this line from your config file:
> 
>> builder = "plan9"
> 
> 

That got me further, thanks. It next dies trying to read then write the
nvram, which is /dev/sd00/nvram in my image. It apparently can't find it.


256# xm create -c plan9.py
Using config file "./plan9.py".

Plan 9
127 holes free
001e5000 04dad000 79462400
79462400 bytes free
cpu0: 1993MHz GenuineIntel PentiumIV/Xeon (cpuid: AX 0x0F27 DX 0xBFEBFBFF)
Started domain plan9
                    #l0: xen: 100Mbps port 0x0 irq -1: aa001000001b
256M memory: 78M kernel data, 178M user, 803M swap
cpu0: spurious interrupt 101, last 0
can't read nvram: unknown device in # filename
authid: bootes
authdom: fubar
secstore key:
password:
can't write key to nvram: fd out of range or not open
boot: can't connect to file server: '#S/sdC0/' file does not exist
panic: boot process died: unknown
panic: boot process died: unknown
dumpstack
ktrace /kernel/path 80014015 801e71f8 <<EOF

Am I missing something from my bootargs?

Thanks,

Mike