[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XenExpress - howto use own build kernel in DomU

  • To: Matthias Meyer <Matthias.Meyer@xxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Sun, 22 Apr 2007 13:19:20 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 22 Apr 2007 05:16:31 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=loJOO8OhzloOYqLvQY3PLkYiHFriK+cd6OYrPBWAJ6S1c8wg88MJqm6IHSbig7+E7clJEP2kX8SK8ZB/9ydpznV9HY4YDT0WwsHvoK0OcMpGuZ4zq1Lg4QiuJwJOboIxcfzX4JuTg5MrUXeh+vANBL4UpSaBT4uZbVT96w1IVck=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Matthias Meyer wrote:

I want to build and use an own kernel in DomU.
I get the kernel-xs-xen/kernel- from the source1 iso and compile it. Because of (unsolved) troubles with mkinitrd I try a build without mkinitrd. I configure /boot/grub/menu.lst within my DomU and restart it. But the old, original, kernel will be started.

How to configure the Dom0 and/or DomU that DomU will start with my customized kernel?

Thanks in advance
Are you using full virtualization, or para-virtualization? If you're using para-virtualization, the DomU kernel must be in place on the *Dom0*, along with its mkinitrd compiled from the /etc/modprobe.conf contents. The DomU need only have the contents of the /lib/modules/[kernel-name], although the full kernel is useful for reference purposes.

If you're using para-virtualization, you're not using grub at all on the DomU and may as well "rpm -e grub" on it to avoid confusion.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.