From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <468C283B.403@sbcglobal.net> Date: Wed, 4 Jul 2007 16:07:39 -0700 From: Mike User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 91323a40-ead2-11e9-9d60-3106f5b1d025 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 <