All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Don Dutile <ddutile@redhat.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	xen-devel@lists.xensource.com
Subject: Re: Help booting Xen under RHEL6 beta2
Date: Fri, 9 Jul 2010 13:44:38 -0400	[thread overview]
Message-ID: <20100709174438.GA10615@phenom.dumpdata.com> (raw)
In-Reply-To: <4C372DA1.4020701@redhat.com>

>       
> > 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
> Not necessarily.  Do this all the time: RHEL6-domU on RHEL5-dom0.
>        ... maybe some intermediate versions of xen dont work w/pv-ops kernel,
>        but it does with rhel5-dom0/xen.
> 
> >    is that fixed in latest xen-4.0-testing?
> good question!  curious minds want to know....

Yes. The xen/evtchn and xen/gntdev are differently created on 2.6.32
and xen-4.0-testing.

For details:
http://lists.xensource.com/archives/html/xen-devel/2010-06/msg01129.html

You can "fix" this by doing:

git revert 376d908f52427591cef4acd172db9c3ef28676ec
and 
git revert 9d85e25edbcb8a684db8470119077475ac4d90b5

That will make it possible for you to use the 2.6.32 with Xen 4.0 (and
earlier versions).

> 
> > 4) Anything else I should watch out for?  E.g. recent
> >    tool changes due to udev or xencommon or ???

There is a bug 1612 for udev. But that is not hit by Fedora 13, but
rather other distros. There is a patch that fixes some of the udev
versions, but not all.

  reply	other threads:[~2010-07-09 17:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 22:16 Help booting Xen under RHEL6 beta2 Dan Magenheimer
2010-07-09  5:30 ` Pasi Kärkkäinen
2010-07-09 14:09 ` Don Dutile
2010-07-09 17:44   ` Konrad Rzeszutek Wilk [this message]
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=20100709174438.GA10615@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=ddutile@redhat.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.