[Xen-devel] Starting DOM1

[Sean Atkinson <sean@xxxxxxxxxxxxxx>]

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.

-- 
Sean Atkinson <sean@xxxxxxxxxxxxxx>
Netproject



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel