7 messages in com.xensource.lists.xen-devel[Xen-devel] Starting DOM1
FromSent OnAttachments
Sean Atkinson22 Mar 2004 02:22 
Keir Fraser22 Mar 2004 02:29 
Sean Atkinson22 Mar 2004 03:45 
Ian Pratt22 Mar 2004 04:02 
Sean Atkinson22 Mar 2004 23:18 
Ian Pratt23 Mar 2004 02:52 
Sean Atkinson25 Mar 2004 01:02 
Subject:[Xen-devel] Starting DOM1
From:Sean Atkinson (se@netproject.com)
Date:03/22/2004 02:22:42 AM
List:com.xensource.lists.xen-devel

Hi,

Now that Keir has fixed xend's event channel device file, I'm getting a little further creating a second domain in Xen. I'm trying to use an NFS root file system from DOM0 to avoid the pain of re-partitioning my disk. I've filled /tmp/root with enough packages to chroot into it, and a writable NFS server is running. Things seem to start OK:

# xc_dom_create.py Parsing config file '/etc/xc/defaults' VM image : "/boot/xenolinux.gz" VM ramdisk : "" VM memory (MB) : "64" VM IP address(es) : "169.254.1.1" VM block device(s) : "" VM cmdline : "ip=169.254.1.1:169.254.1.0:192.168.1.1:255.255.255.0::eth0:off root=/dev/nfs nfsroot=/tmp/root " VM started in domain 7. Console I/O available on TCP port 9600.

For a bit "xc_dom_control.py list" includes the new domain, but soon it disappears. xen_dmesg.py only reports the killing the domain and releasing the task. I get no output at all from "console_client.py 168.254.1.0 9600", or with DOM1's IP address.

Am I doing something obviously wrong, or are there any more diagnostics I can try please?

Thanks,

Sean.