xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: xen-devel@lists.xensource.com
Cc: Konrad Wilk <konrad.wilk@oracle.com>
Subject: Help booting Xen under RHEL6 beta2
Date: Thu, 8 Jul 2010 15:16:23 -0700 (PDT)	[thread overview]
Message-ID: <1e22d374-43a0-4fe9-bea4-65511d0e0430@default> (raw)

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-2.6.31.13
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.

Thanks,
Dan

             reply	other threads:[~2010-07-08 22:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 22:16 Dan Magenheimer [this message]
2010-07-09  5:30 ` Help booting Xen under RHEL6 beta2 Pasi Kärkkäinen
2010-07-09 14:09 ` Don Dutile
2010-07-09 17:44   ` Konrad Rzeszutek Wilk
2010-07-09 18:09     ` M A Young
2010-07-09 20:01       ` Konrad Rzeszutek Wilk
2010-07-09 22:48         ` Dan Magenheimer
2010-07-09 23:27           ` M A Young
2010-07-10 21:42             ` Dan Magenheimer
2010-07-11  2:24               ` Dan Magenheimer
2010-07-12 10:37                 ` Stefano Stabellini
2010-07-12 13:59                   ` Dan M @ Oracle
2010-07-12 14:06                     ` Stefano Stabellini
2010-07-12 14:30                       ` Keir Fraser
2010-07-12 14:37                       ` Ian Campbell
2010-07-12 20:19                         ` Dan Magenheimer
2010-07-12 20:38                           ` Keir Fraser
2010-07-12 20:44                             ` Dan Magenheimer
2010-07-12 21:10                               ` Keir Fraser
2010-07-12 21:36                                 ` Dan Magenheimer
2010-07-13  6:19                                   ` Keir Fraser
2010-07-13  0:39                             ` Dan Magenheimer
2010-07-13  1:30                               ` Konrad Rzeszutek Wilk
2010-07-13 23:55                                 ` Dan Magenheimer
2010-07-14 15:31                                   ` Dan Magenheimer
     [not found] <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@defaultC8613BEA.3186%keir.fraser@eu.citrix.com>

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=1e22d374-43a0-4fe9-bea4-65511d0e0430@default \
    --to=dan.magenheimer@oracle.com \
    --cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).