From: Sassy Natan <sassyn@gmail.com>
To: Josip Rodin <joy@entuzijast.net>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xen.git plans / 2.6.32 long-term stable kernel
Date: Mon, 25 Jan 2010 22:48:59 +0200 [thread overview]
Message-ID: <529a12f41001251248y44193605xb0ff6a2f7816526f@mail.gmail.com> (raw)
In-Reply-To: <20100125133845.GA8968@orion.carnet.hr>
[-- Attachment #1.1: Type: text/plain, Size: 2193 bytes --]
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@entuzijast.net> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 3022 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-01-25 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 20:59 xen.git plans Jeremy Fitzhardinge
2010-01-20 10:18 ` xen.git plans / 2.6.32 long-term stable kernel Pasi Kärkkäinen
2010-01-20 18:40 ` Jeremy Fitzhardinge
2010-01-20 18:55 ` Pasi Kärkkäinen
2010-01-25 20:37 ` Sassy Natan
2010-01-27 11:32 ` Josip Rodin
2010-01-27 11:41 ` Pasi Kärkkäinen
2010-01-25 13:38 ` Josip Rodin
2010-01-25 20:48 ` Sassy Natan [this message]
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=529a12f41001251248y44193605xb0ff6a2f7816526f@mail.gmail.com \
--to=sassyn@gmail.com \
--cc=jeremy@goop.org \
--cc=joy@entuzijast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).