WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen.git plans / 2.6.32 long-term stable kernel

To: Josip Rodin <joy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen.git plans / 2.6.32 long-term stable kernel
From: Sassy Natan <sassyn@xxxxxxxxx>
Date: Mon, 25 Jan 2010 22:48:59 +0200
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 25 Jan 2010 12:49:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=lQLDwTPSW3Kitdk2lgsB6vZh65S6XNlUv+AIWBWXzeQ=; b=OPW91SGHWvcU4XApEnfUYgsDmuZoi8jgdXfJrdiOdC69QmyzGog9uFCx0E3XqDVuVU efB64U6IO5RBYEETyLcRSBFOrW7XbgB9nzT5ZcdTqutUTqyhs55YP57bgo3bu+YlTvo4 s7Bt0oqrggGLdmYRUSLkcgamFoFRC2drW8s5c=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=T6V1cnOunTvDZ0oZbhqSXGFBA2HIwNOcbQPpP801ItbBhsdz0LFg2DVRutynjDwMRI L/MaX4EIU1DDwZ/jVXldSe78tVPDSiqJ1fhsSRrebLM5S/ISea7uZcNxJhO31t2CgvEx 1pwOSidb4t7yMBESH2F3tG65ABLeUkucruli8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100125133845.GA8968@xxxxxxxxxxxxxxx>
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>
References: <4B313331.7060604@xxxxxxxx> <20100120101834.GN2861@xxxxxxxxxxx> <4B574E02.8020204@xxxxxxxx> <20100125133845.GA8968@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Did u find kernel 2.6.31.6+paravirt_ops dom0 and Xen 3.4.2 I guess stable enough?
I did found some issues with domain restore, but indeed this seems like the best virtualization systems.
 
Thanks
Sassy


 
On Mon, Jan 25, 2010 at 3:38 PM, Josip Rodin <joy@xxxxxxxxxxxxxx> wrote:
On Wed, Jan 20, 2010 at 10:40:02AM -0800, Jeremy Fitzhardinge wrote:
> On 01/20/2010 02:18 AM, Pasi Kärkkäinen wrote:
>> It seems Linux 2.6.32 will be a long term supported stable release,
>> ending up in multiple distros..
>>
>> Distros that are probably going to use it:
>>
>>      - Debian 6.0 ("Squeeze")
>>      - Ubuntu 10.04 LTS ("Lucid Lynx")
>>      - RHEL6
>>
>> Please correct me if I'm wrong :)
>>
>> kernel.org developers are also going to make 2.6.32 a long-term stable release.
>> (announced yesterday).
>
> Yep, that all works out nicely doesn't it?

Can you please update xen.git to have a branch based off
stable/linux-2.6.32.y.git ? Right now it's still a stable .31.6 and mainline
.32-rc5 in there, so we're missing a couple of months worth of bug fixes.

Since this kernel is going to enter so many stable distribution releases,
it would really be a good idea to get that exact combination widely tested
'in the wild'.

I'm asking particularly because the current Debian dom0 kernel (based on
.18 patches forward-ported onto .26) turned out to have a major regression
issue described in http://bugs.debian.org/534880 that didn't even get
reported until months after the release. Perhaps this particular bug is
specific to the old branch, but then the new paravirt_ops branch may have
some other, newer bugs of its own, so it makes sense to encourage widespread
testing as soon as possible.

My own 2.6.31.6+paravirt_ops dom0 test machine is still working great after
several months, so I'm optimistic. Thanks for all the hard work that made it
happen.

--
    2. That which causes joy or happiness.

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

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