Re: [Xen-devel] Xen dom0 Kernel Patches

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Thu, Jun 04, 2009 at 10:55:44AM -0700, Boris Derzhavets wrote:
> Through my experience xenified kernel been built on 
>    # hg clone http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg
> works  fine under Xen 3.3.1,3.4,3.5-unstable.
> However, attempt to shutdown Xen Host causes dropping into stack trace.
> Kernel 2.6.29.4 with rebased patches suggested by Andy Lyon allows to
> shutdown Xen Host cleanly.
> 

Ian proposed the _other_ 2.6.27-xen tree from XCI project:
http://xenbits.xen.org/XCI/

-- Pasi

> Boris.
> 
> --- On Thu, 6/4/09, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx> wrote:
> 
> From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
> Subject: RE: [Xen-devel] Xen dom0 Kernel Patches
> To: "Pasi Kärkkäinen" <pasik@xxxxxx>, "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
> Cc: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>, "Xen-devel" 
> <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Thursday, June 4, 2009, 11:08 AM
> 
> > Are you willing to maintain such patchsets? The temporary 2.6.27-xen tree
> > made for Novell/SuSE guys is totally unmaintained..
> 
> The 2.6.27 git tree and patchqueue under the Xen Client Initiative directory 
> on xenbits is fairly well maintained: http://xenbits.xen.org/XCI/
>  
> To my mind this would be a better default tree for us to use for xen-unstable 
> than the ancient 2.6.18. We obviously want to continue to encourage folk to 
> try Jeremy's pvops dom0 stable tree based off the latest linux release too. 
> 
> Ian
> 
>  
> > I think most of the development effort should be used on getting pv_ops
> > dom0 ready for
> > mainline, but if you (for example), want to maintain forward-ported patches
> > for new kernel versions, it sounds like a good idea.. for the time being.
> > 
> > -- Pasi
> > 
> > _______________________________________________
> > 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
> 
> 
> 
>       

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