We are happily running xen on a server which uses a SATA driver (thank you all you xenists for producing such a great product). However, we are creating a custom kernel for a domU. When we attempt to run mkinitrd we get: No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. This is the SATA driver. In the past (xen 2.0.5), we simply ran make ARCH=xen menuconfig and told it to build a module for the low level scsi driver for ata_piix. That was simply to eliminate the error as I do not think the domU actually needs the SATA driver. However, in xen 2.0.7 with the 2.6.11.12 kernel, this option is no longer available. That''s not so bad since I''m sure we were not addressing the real issue in our work around. What is the real issue and how do we eliminate this error? On a related note, we always notice kudzu on boot and tell it to remove the configuration for a number of devices which are now virtualized be they keyboard drivers or NIC drivers. How do we eliminate those? Thanks - John -- John A. Sullivan III Open Source Development Corporation +1 207-985-7880 jsullivan@opensourcedevel.com If you would like to participate in the development of an open source enterprise class network security management system, please visit http://iscs.sourceforge.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John A. Sullivan III wrote:> We are happily running xen on a server which uses a SATA driver (thank > you all you xenists for producing such a great product). However, we > are creating a custom kernel for a domU. When we attempt to run > mkinitrd we get: > > No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. > > This is the SATA driver. In the past (xen 2.0.5), we simply ran make > ARCH=xen menuconfig and told it to build a module for the low level scsi > driver for ata_piix. That was simply to eliminate the error as I do not > think the domU actually needs the SATA driver. >This is a configuration issue with mkinitrd. Configuring mkinitrd to exclude modules you don''t need in domU''s should fix this issue. Remember, you''re building an initial ram disk for a domU and not dom0, so you don''t need many modules. -- Jeff McCune OSU Department of Mathematics System Support (614) 292-4962 gpg --keyserver pgp.mit.edu --recv-key BAF3211A _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, 2005-11-07 at 10:33 -0500, Jeff McCune wrote:> John A. Sullivan III wrote: > > We are happily running xen on a server which uses a SATA driver (thank > > you all you xenists for producing such a great product). However, we > > are creating a custom kernel for a domU. When we attempt to run > > mkinitrd we get: > > > > No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. > > > > This is the SATA driver. In the past (xen 2.0.5), we simply ran make > > ARCH=xen menuconfig and told it to build a module for the low level scsi > > driver for ata_piix. That was simply to eliminate the error as I do not > > think the domU actually needs the SATA driver. > > > > This is a configuration issue with mkinitrd. Configuring mkinitrd to > exclude modules you don''t need in domU''s should fix this issue. > Remember, you''re building an initial ram disk for a domU and not dom0, > so you don''t need many modules.That''s what I would have thought. Pardon my ignorance but how does one configure mkinitrd to exclude these modules? Thanks - John <snip> -- John A. Sullivan III Open Source Development Corporation +1 207-985-7880 jsullivan@opensourcedevel.com Financially sustainable open source development http://www.opensourcedevel.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John A. Sullivan III wrote:>>>We are happily running xen on a server which uses a SATA driver (thank >>>you all you xenists for producing such a great product). However, we >>>are creating a custom kernel for a domU. When we attempt to run >>>mkinitrd we get: >>> >>>No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. >>> >>>This is the SATA driver. In the past (xen 2.0.5), we simply ran make >>>ARCH=xen menuconfig and told it to build a module for the low level scsi >>>driver for ata_piix. That was simply to eliminate the error as I do not >>>think the domU actually needs the SATA driver. >>> >> >>This is a configuration issue with mkinitrd. Configuring mkinitrd to >>exclude modules you don''t need in domU''s should fix this issue. >>Remember, you''re building an initial ram disk for a domU and not dom0, >>so you don''t need many modules. > > > That''s what I would have thought. Pardon my ignorance but how does one > configure mkinitrd to exclude these modules? Thanks - John > <snip>configuring mkinitrd is a distribution specific issue. Check man mkinitrd for your dom0 distribution. mkinitrd is tricky because it assumes you''re making an initial ram disk for the system you''re on (dom0) but you actually want to configure it for the domU which is compltely different. -- Jeff McCune OSU Department of Mathematics System Support (614) 292-4962 gpg --keyserver pgp.mit.edu --recv-key BAF3211A _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/7/05, Jeff McCune <mccune@math.ohio-state.edu> wrote:> John A. Sullivan III wrote: > >>>No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting.I run into the same problems as you with the CentOS (RedHat) distribution. What I do is the following: mkinitrd --builtin=ata_piix -f <path_to_initrd_image> <kernel_version> I usually build in all the modules I can statically into the kernel so I don''t have to deal with module dependencies. HTH, - gino ledesma _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users