From: "David F. Barrera" <dfbp@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: linux-2.6-xen kernels and initrds
Date: Thu, 30 Mar 2006 16:12:26 -0600 [thread overview]
Message-ID: <442C57CA.3040307@us.ibm.com> (raw)
I have a question regarding the building of the unified xen kernel
(linux-2.6-xen) and the use of initrd. In the past I built both xen0
and xenU kernels; the xen0 default configurations had SCSI and Fusion
MPT support compiled into the kernel. Now, they are built as modules.
The problem is that I am unable to boot the xen kernel built that way,
even though I am building an initrd. I have machines running both SLES
and FC that are exhibiting this problem. The question is, do I need to
do something special to build the initrds? In SuSE, I typically just
used the 'mkinitrd' command; in FC4, I do it like this: "mkinitrd -v -f
--with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen
2.6.16-xen". At any rate, nothing has worked to this point.
The SCSI device support help page in 'make menuconfig' states 'do not
compile this as a module if your root file system (the one containing
the directory /) is located on a SCSI device.', which is the case in my
setup. But I have seen it where the distros compile it as module, and
the initrd takes care of it.
Any help would be appreciated.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next reply other threads:[~2006-03-30 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 22:12 David F. Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-30 23:27 linux-2.6-xen kernels and initrds Andrew D. Ball
2006-03-30 23:47 Puthiyaparambil, Aravindh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=442C57CA.3040307@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.