xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 15:32:38 +0100	[thread overview]
Message-ID: <C7D91B96.F597%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <a0d1288d-7059-4836-84e6-802ad67d9feb@default>

On 31/03/2010 15:20, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

>>> Can you shed some light on this issue -- why is this kernel repo
>> there,
>>> and what kernel will *really* be the official and stable option for
>> Xen 4?
>>> What will be part of the next week release?
> 
> Keir already answered this tersely, but let me explain further
> (and others can correct me if I am wrong).  There IS NO official
> dom0 for Xen 4.0 from xen.org.  Xen 4.0 is a hypervisor not
> a virtualization distro.  Similarly, Linux 2.6.33 is a kernel release,
> not an OS distro.  Distros of both are free to choose whatever other
> components work best for their customers.

Yes, that's pretty much the situation. Basically, when moving to 4.0 there
is no need to change any dom0 or domU kernel (unless you want to use certain
new features like Remus or blktap2, and your current dom0 doesn't have the
required bits). Of course that doesn't mean we abdicate responsibility for
producing high-quality kernels for running on Xen -- or at least HQ
Xen-specific bits that can then be pulled into HQ kernel releases by
distros. I think trying to publish "kernel releases" for end users would
actually be a dangerous thing for us to do, unless we were also prepared to
deal with things like security updates in a timely fashion, and we haven't
got a channel for distributing that kind of thing in the same effective way
that distros have.

 -- Keir

  reply	other threads:[~2010-03-31 14:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54   ` Keir Fraser
2010-03-31 11:00     ` Joanna Rutkowska
2010-03-31 11:13       ` Keir Fraser
2010-03-31 12:38       ` Ian Pratt
2010-03-31 14:20         ` Dan Magenheimer
2010-03-31 14:32           ` Keir Fraser [this message]
2010-03-31 14:44           ` Ian Pratt
2010-03-31 19:55           ` Grant McWilliams
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09   ` Keir Fraser
2010-03-31 15:44     ` Bastian Blank
2010-03-31 16:38       ` Keir Fraser
2010-03-31 18:03         ` Konrad Rzeszutek Wilk
2010-03-31 18:18           ` Keir Fraser
2010-03-31 20:40             ` Jeremy Fitzhardinge
2010-03-31 19:10 ` Konrad Rzeszutek Wilk
2010-03-31 19:33   ` Keir Fraser
2010-03-31 19:52     ` Konrad Rzeszutek Wilk
2010-03-31 20:07       ` Keir Fraser
2010-03-31 21:07         ` Konrad Rzeszutek Wilk
2010-05-19 12:10           ` Keir Fraser
2010-05-26 15:02             ` Konrad Rzeszutek Wilk

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=C7D91B96.F597%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=joanna@invisiblethingslab.com \
    --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).