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" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Friday 01 July 2005 04:30, sten wrote:> 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.Maybe I''m not up to date here, but does 2.0.6 even support having PCI devices in domains other than xen0 ? Thought that feature was planned for xen 3? Greetings /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 30 Jun 2005 21:30:53 -0500 sten <lists@redboy.cx> wrote:> 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. > 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 > >Hi Sten, what I would do is put the domU kernel straight into the boot loader (grub) and test wether it works without xen. Sincerely, Jan. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Maybe I''m not up to date here, but does 2.0.6 even support > having PCI devices in domains other than xen0 ? > > Thought that feature was planned for xen 3?No, that works fine in 2.0.6 Its actually broken in 3.0 right now because of the major PCI/ACPI changes, and has yet to be fixed as no one is screaming for it. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Smith wrote:> On Thu, 30 Jun 2005 21:30:53 -0500 > sten <lists@redboy.cx> wrote: > > >>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. >>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 >> >> > > > Hi Sten, > > what I would do is put the domU kernel straight into the boot > loader (grub) and test wether it works without xen. > > Sincerely, > > Jan.Attempting to boot my xenU kernel straight from GRUB results in a "unsupported or invalid executable" message; this occurs with both XenU and Xen0 kernels, and I assume it''s expected behavior since the kernels are compiled for the Xen architecture rather than i386. Feel free to beat me with a trout if I''m wrong on this. I went back and tried using my XenU kernel as dom0, which promptly failed with "not syncing: VFS". I built an initrd image for the XenU kernel, and then I was able to boot with the XenU kernel as dom0; I got to a command prompt and could log in. I bounced back into my original Xen0 kernel, added a "ramdisk = " line to my xenu config file, re-ran xm create -c myfile, and, again, it sat and did nothing. Maybe the problem isn''t the kernel after all; I''ve tried two types of VBDs, file-backed and LVM. I created an LVM image with debootstrap, and created the file-backed VBD by dd''ing the contents of my LV into a file. I also tried using the process for creating a file-backed VBD in the Xen user guide verbatim, and same result. Is there a more foolproof way of creating a VBD I could try? Thanks! -sten _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users