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] Future of xenbits Linux trees

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Future of xenbits Linux trees
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Fri, 5 Jun 2009 08:32:21 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 05 Jun 2009 00:33:05 -0700
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 :content-transfer-encoding; bh=fxrYTDJPB0i170Xfs5GDRXjfisqrc4USToe0aMPRl4c=; b=Z80oujEXa4yf9GczupUzNtN5ODCF/K6tia73W31kXt5iQc0sfRAc4z2/OgqMQXFNgZ NiWsIWjHJEAE+I51sgVfrohBA7fOiJcbyBVW/nHEhNu46wnZ7bA82BArpAxbGMO9pQbP gFKPPL52WS+hPthf4rvvMiJlwc0I9MCzmc0bg=
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:content-transfer-encoding; b=Vdk4Pl78Cl2ED+x1XpzWWpP1wgNuzfhgSe2mspjSUbL1/kxtAu8kPgMh45BcNf3WPa Ab750iLjDBvF6Y6PLEie4Z7srA0+P0LbbC5pC7XUAubWrWu4y06coJRNjbjUx61iFxG+ LxFsQkhkw6rfdnTfjrDTY3qEUoGTrR+ySw0H4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C64DAAA6.788E%keir.fraser@xxxxxxxxxxxxx>
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: <C64DAAA6.788E%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Jun 4, 2009 at 4:45 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> Folks,
>
> With 3.4 out the door it is time to revisit the state of our Linux
> repositories. Currently we have a number of trees in various states of
> maintenance:
>  - linux-2.6.18-xen.hg: the 'original' tree. Still maintained, used and
> tested but increasingly long in the tooth.
>  - ext/linux-2.6.27-xen.hg: a snapshot of opensuse's kernel port. This
> clones tree is not maintained or tested.
>  - XCI/linux-2.6.27.git: a forward port of the Xen patches to 2.6.27.
> Maintained as part of XCI project.
>  - Jeremy's pv_ops patches against kernel.org: maintained, (somewhat)
> tested, but incomplete.
>
> It is probably time to kill the 2.6.18 tree, or at least stop active
> development within it. It is increasingly a kludged collection of backports
> of more recent kernel patches, and is also missing a lot of drivers for more
> modern hardware.
>
> Our proposal is to move XCI's linux-2.6.27 tree out of the XCI subproject
> and make it the main user tree. Development and automated testing would
> occur on that tree and of course on Jeremy's pv_ops patchset (which we want
> to completely move onto at some point in the future).
>
> What do people think of this as a plan?
>
>  -- Keir

I think 2.6.27 is already out of date and you should start with 2.6.29
using my rebased patches, people have been using them since I did
2.6.25 and 2.6.29 is the most stable one yet, as Boris said in another
thread the xenbits 2.6.27 tree does not shutdown cleanly but 2.6.29
does, I'm sure that could be fixed but right now I dont know of any
issues with 2.6.29 at all, so why not make the jump to the current
stable kernel :).

XCI should update to 2.6.29 as well.

I use pci passthrough with a pci express usb2 card, I also use scsi
passthrough with a ultrium tape drive, usually running several windows
hvm's and a couple of 2.6.29 pv domU's as well, no problems.

Andy

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