From: Nils Toedtmann <xen-devel@nils.toedtmann.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen-2.0 + linux-2.6.15?
Date: Tue, 28 Feb 2006 13:12:32 +0100 [thread overview]
Message-ID: <1141128753.17186.35.camel@localhost> (raw)
In-Reply-To: <bd5e1401a2d8dde79cd0c538a0abab6e@cl.cam.ac.uk>
Am Dienstag, den 28.02.2006, 10:43 +0000 schrieb Keir Fraser:
> On 28 Feb 2006, at 10:25, Nils Toedtmann wrote:
>
> > I have a very stable xen-host with several domUs (uptimes > 300d).
> >
> > It's still 2.6.11.x + xen-2.0 and now i'd like to upgrade it to
> > 2.6.15.4. I have to do that remotely, and xen-2.0 was absolutely ok for
> > me (rock-solid!), so i'd like to stick with xen-2.0 for now. But the
> > last Changeset of the xen-2.0-testing hg tree is 3520 from 2005-12-28,
> > and it still wants linux-2.6.12.
> >
> > Do i have to choose between 2.6.12.x+xen-2.0 and 2.6.15.x+xen-3.0?
> >
> > What about a maintenance release 2.0.8 for linux-2.6.15 or upcoming
> > -2.6.16?
>
> At the moment you have to make that choice.
That's a choice between two evils ... any experiences comparing
stability of 2.0 vs. 3.0? (Of cause there is no xen-3.0.x system with
uptime>90d ;-)
> It would be great if someone upgraded the 2.0 kernel,
true
> but the core developers are busy with 3.0.
Comprehensible. So no xen-2 release on the roadmap? Then i'll have to
move to xen-3, too many sec issues with < 2.6.15.4 :(
/nils.
ps: xen is great, thank you for this wonderful piece of software!
next prev parent reply other threads:[~2006-02-28 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 10:25 xen-2.0 + linux-2.6.15? Nils Toedtmann
2006-02-28 10:43 ` Keir Fraser
2006-02-28 12:12 ` Nils Toedtmann [this message]
2006-02-28 13:14 ` Keir Fraser
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=1141128753.17186.35.camel@localhost \
--to=xen-devel@nils.toedtmann.net \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.