I'm finally getting to play with Xen, and my plan is to stick all my PCI
devices into a few dedicated xenU domains; I'm starting with the easy
stuff, setting up a Xen guest kernel to manage my physical NICs.
I grabbed 2.0.6, did a 'make dist', then copied my existing kernel
config from Debian into the xenU directory and made dist again. After
some tweaking to get unsupported ISA modules out of the config, the
kernel built, and I did a 'make install'.
I created a filesystem on a locgical volume, set it up with debootstrap,
created a config for my xenU, and rebooted.
Now, I can boot into Xen, xen0 comes up, and I can start xend, but when
I try to start my xenU instance with xm create -c, I get connected to a
remote console, and that's as far as it goes. In xm log, I see that xend
creates the console, then the domain, unpauses the domain, connects the
console, then right away XendDomain>reap says the domain died.
I tried changing my domain config file so that it pointed at my Xen0
kernel, and that booted just fine, so obviously I suspect my custom xenU
kernel. I hate to be so broad, but all I know at this point is "it
doesn't work." Does anyone have any tips on building a xenU kernel with
approximately everything available built as modules, and/or why my
instance doesn't boot? I've included my instance config file and
attached my xenU kernel config.
Thanks!
-sten
instance config file:
kernel = "/boot/vmlinuz-2.6.22.20-xenU"
memory = 64
name = "test"
cpu = -1
nics = 0
disk = [ 'phy:datavg/testlv,sda1,w' ]
root = "/dev/sda1 ro"
xenu_config.gz
Description: GNU Zip compressed data
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home