[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Basic Question
> If I use the create a config in /etc/xen and refer to say kernel > ="/boot/vmlinuz-2.6.11-1.1369_FC4xenU" where do I add extra flags > during bootup, i.e selinux=0. Do I add it to the end of this line > like: > > kernel ="/boot/vmlinuz-2.6.11-1.1369_FC4xenU selinux=0" or do I need > to add to a grub.conf file in the domU? IIRC, this sort of thing should go in the "args" variable of the config file - this gets appended to the kernel command line when the domain is started. kernel= is just the path to the kernel within the dom0 ("host") filesystem. You don't need a grub.conf in the guest but in the -unstable tree you can create one in the guest filesystem and get a bootloader prompt when you start the domain. In this case, the guest kernel will need to be *inside* the guest filesystem for the bootloader to find it. I'm not sure but there may be some config options required to enable the guest bootloader. Cheers, Mark > Thanks > Shaz > > On 6/15/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote: > > > Whats the difference between the xenU and xen0 kernel. Is there a > > > technical difference, does this relate to how xen works? Can some one > > > please give me a little summary of how it works. > > > > The xen0 kernel contains all the drivers required to run in a domU > > (unprivileged guest) *and* all the drivers required to run in dom0 (i.e. > > privileged command interface, device drivers for the real hardware, > > etc.). This'll run in *any* domain. > > > > The xenU kernel contains only the drivers required to run in a domU - no > > privileged command interface, no drivers for real hardware. The only > > practical difference is that this kernel is a few hundred kilobytes > > smaller but can only run in domUs. > > > > HTH, > > Mark _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |