This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Help booting Xen under RHEL6 beta2

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Help booting Xen under RHEL6 beta2
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 8 Jul 2010 15:16:23 -0700 (PDT)
Cc: Konrad Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 08 Jul 2010 15:20:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
With RHEL6 beta 2 now available, I am once again trying
to get a fresh Xen 4.0-testing tree booted "underneath" it.
(This is for my Xen development machines, no political
comments please ;-)  I'm sure there are some similarities
between this process and the process under FC13(?);
any help appreciated.

I have cloned xen-4.0-testing.hg and successfully built
a full set of Xen "stuff" with "make world".  The dom0
kernel that is installed in /boot is vmlinuz-
I used the default config (and default responses to
the "make oldconfig" that seems to be run by default)
to build this dom0 kernel.

1) Is there a better config file to start from for
   building the dom0 kernel?  For example, I see that
   CONFIG_SYSFS_DEPRECATED{,V2} are not set, and I
   am fairly confident that this kernel will not boot
   a RHEL6 environment without it.
2) What do I use to build the initrd?  The standard
   "mkinitrd initrd.img version" yields LOTS of error
   messages and, in any case, I believe that dracut
   should now be used instead of mkinitrd?
3) Should I be using a different/newer pvops kernel?
   IIRC, there is an issue with booting >=2.6.32
   pvops dom0 with pre-xen-unstable hypervisors? Or
   is that fixed in latest xen-4.0-testing?
4) Anything else I should watch out for?  E.g. recent
   tool changes due to udev or xencommon or ???

Most of these final steps are black magic to me and
I've been using a recipe on RHEL5uX for them for
so long, I'm not even sure what to look for if
(when) the dom0 boot fails... and trial and error
is not very productive for this kind of thing.


Xen-devel mailing list