Xen readers - Been trying to get xen working on FC6 for some time now, and i am not sure what i am doing wrong - last time i played with xen it was v2 and didnt seem to be this difficult to get working. ANyway, thought i would see if there was a kind soul that could give me some guidance. I have a Fedora Core 6 server running the latest kernel 2.6.19-1.2911.6.5 and xen 3.0.3-6 and i have a few dom''s i grabbed from jailtime.org to play with (i.e. debian-3.1, centos-4.4, etc). I am specifically trying to get the debian dom running, here is the config: kernel = "/boot/vmlinuz-2.6.19-1.2911.fc6xen" memory = 128 name = "debian.3-1" vif = [''''] dhcp = "dhcp" disk = [''file:/xen/debian/debian.3-1.img,hda1,w'', ''file:/xen/debian/debian.swap,hda2,w''] root = "/dev/hda1 ro" pretty generic, and when i go to fire it up with ''xen create debian-3.1.cfg-c'' it starts up and runs for a few moments then dies, leaving the following in the log file: Mar 19 11:06:19 monica kernel: xenbr0: port 3(vif11.0) entering disabled state Mar 19 11:06:19 monica kernel: device vif11.0 left promiscuous mode Mar 19 11:06:19 monica kernel: audit(1174316779.413:26): dev=vif11.0 prom=0 old_prom=256 auid=4294967295 Mar 19 11:06:19 monica kernel: xenbr0: port 3(vif11.0) entering disabled state Mar 19 11:06:21 monica kernel: device vif12.0 entered promiscuous mode Mar 19 11:06:21 monica kernel: audit(1174316781.232:27): dev=vif12.0prom=256 old_prom=0 auid=4294967295 Mar 19 11:06:21 monica kernel: ADDRCONF(NETDEV_UP): vif12.0: link is not ready Mar 19 11:06:25 monica kernel: xenbr0: port 3(vif12.0) entering disabled state Mar 19 11:06:25 monica kernel: device vif12.0 left promiscuous mode Mar 19 11:06:25 monica kernel: audit(1174316785.144:28): dev=vif12.0 prom=0 old_prom=256 auid=4294967295 Mar 19 11:06:25 monica kernel: xenbr0: port 3(vif12.0) entering disabled state Not really sure what the heck its complaining about. The server i am running this on has a single network card with a single IP address so i really dont have spare IPs i can throw at this thing. First thing, what am i doing wrong? And does anyone have any suggestions on the best way to run this? Or a good link that i can reference? Just seems v2 was easier to get this to work without much magic, but i am getting old, and may not be remembering all the details too well - its been awhile since i have played with it. Thanks in advance Michael Weiner
On Mon, Mar 19, 2007 at 11:16:48AM -0400, Michael Weiner wrote:> Xen readers - > > Been trying to get xen working on FC6 for some time now, and i am not sure > what i am doing wrong - last time i played with xen it was v2 and didnt seem > to be this difficult to get working. ANyway, thought i would see if there > was a kind soul that could give me some guidance. I have a Fedora Core 6 > server running the latest kernel 2.6.19-1.2911.6.5 and xen 3.0.3-6 and i > have a few dom''s i grabbed from jailtime.org to play with (i.e. debian-3.1, > centos-4.4, etc). I am specifically trying to get the debian dom running, > here is the config: > > kernel = "/boot/vmlinuz-2.6.19-1.2911.fc6xen" > memory = 128 > name = "debian.3-1" > vif = [''''] > dhcp = "dhcp" > disk = [''file:/xen/debian/debian.3-1.img,hda1,w'', > ''file:/xen/debian/debian.swap,hda2,w''] > root = "/dev/hda1 ro"You''ve not provided any initrd. All Fedora kernels (both Xen & baremetal) are fully modular, so you need to create a suitable initrd containing whatever kernel modules you might need to boot with (eg the Xen drivers for disk access). You''ll also need to install the kernel inside the guest FS so that any kernel modules needed later in boot process are available. In general we recommend using the Xen kernel distributed by the OS distributor themselves, rather than mixing & matching kernels & OS images from different distributions.> pretty generic, and when i go to fire it up with ''xen create > debian-3.1.cfg-c'' it starts up and runs for a few moments then dies, > leaving the following > in the log file:The system logs generally don''t contain any useful information relating to Xen. You should instead look at the Xen logs - /var/log/xen/* Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|