Re: [Xen-users] RE: Fully virtualized guest boot problem

["Daniel P. Berrange" <berrange@xxxxxxxxxx>]

On Mon, Feb 12, 2007 at 03:35:36PM +0100, Petersson, Mats wrote:
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of anant
> > Sent: 12 February 2007 14:24
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] RE: Fully virtualized guest boot problem
> > 
> > 
> > >I don't see anything wrong in the configuration or the log messages.
> > 
> > Yeah same here...I dont think anything is wrong with the 
> > config. So thats
> > the reason i suggested him other distro so that if he couldnt 
> > get hold of
> > the problem, he could move onto more stable version of Xen with stable
> > distro if changing distro is not a problem.
> 
> Yes, but another option would be to use the stable xen releases from
> XenSource. Most distro's use a "snapshot+bugfixes" approach to their
> builds - they can't always sync their releases with the XenSource stable
> releases, and thus will have to "live with" back-porting and patching
> some particular version of Xen [just grabbing a new "latest" isn't a
> good idea when stabilizing for release, cherry-picking the "best" of the
> latest patches is a much better way - otherwise you may get some new
> "badness" when fixing a particular problem]. 

That's not true for Fedora / RHEL at least - we always try to sync up
on official Xen releases - for FC6 / RHEL-5 we're on Xen 3.0.3 and for
F7 we're on 3.0.4. There are a number of bug fixes we backport to the
official releases for important problems, but we try to minimise the
patches carried because of the support burden this entails. 

Syncing with official Xen releases isn't really a problem - one just picks
the most recent release just before the distro feature freeze. The biggest
problem by an *order of magnitude* is that official Xen releases are based
obsolete upstream kernel trees.  So there is huge work involved in forward
porting Xen kernel patches to a up2date LKML kernel tree :-(  Updating
xen-unstable.hg to 2.6.18 was a small step forward, but that will still
leave Xen 3.0.5 trailing LKML by at least 2 releases, so doesn't really
help reduce workload for the distributors *all* of whom are shipping
forward ports of Xen rather than the outdated official trees.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users