xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: marmarek@invisiblethingslab.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.1.x security support
Date: Wed, 18 Sep 2013 10:50:51 +0200	[thread overview]
Message-ID: <5239696B.7070209@invisiblethingslab.com> (raw)
In-Reply-To: <523982DC02000078000F4420@nat28.tlf.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1621 bytes --]

On 09/18/13 10:39, Jan Beulich wrote:
>>>> On 17.09.13 at 19:44, Joanna Rutkowska <joanna@invisiblethingslab.com> wrote:
>> And a somehow more general thought: what most people expect from
>> baremetal hypervisors, I think, is stability. Unlike the Linux kernel,
>> the Xen hypervisor does not need to support each and every device
>> invented on the planet, each and every possible filesystem, or
>> networking stack, etc. That's, in fact, (one of) the biggest advantage
>> of a hypervisor over a monolithic kernel. So, why, oh why, such a race
>> to keep bumping the major version over and over again?
> 
> In fact I'm the (so far apparently only) one trying to stop further
> accelerating the release schedule from its original 9 month cycle.
> I don't recall you having chimed in when the release schedule for
> 4.4 in particular and the shortening of the release cycle in general
> was discussed on the mailing list. There were arguments in favor
> of the shortening which I certainly appreciate.
> 

Well, I'm not regular on xen-devel, because I'm not a Xen developer,
really. I'm a _user_ of Xen. In an ideal world we (Qubes OS project)
should not even maintain a fork of Xen, nor be at xen-devel at all.

I just came here now because I'm worried that the team I'm leading, the
users of Xen, will now need to spend considerable amount of time on
upgrading our product to Xen 4.2, because Xen 4.1 security support is
ending soon. I can imagine there are more users of Xen who would share
my worries, hopefully they will come to this threat sooner or later and
back me up :)

joanna.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-09-18  8:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 22:01 Xen 4.1.x security support Marek Marczykowski-Górecki
2013-09-17  6:47 ` Jan Beulich
2013-09-17 17:38   ` Joanna Rutkowska
2013-09-17 17:44     ` Joanna Rutkowska
2013-09-17 19:18       ` Ian Campbell
2013-09-17 19:55         ` Joanna Rutkowska
2013-09-17 20:36           ` Marek Marczykowski-Górecki
2013-09-17 20:50             ` Ian Campbell
2013-09-17 20:46           ` Ian Campbell
2013-09-18 10:03           ` Vincent Hanquez
2013-09-18 10:08             ` Joanna Rutkowska
2013-09-18  8:39       ` Jan Beulich
2013-09-18  8:50         ` Joanna Rutkowska [this message]
2013-09-18  9:19         ` Sander Eikelenboom
2013-09-18 15:50           ` George Dunlap
2013-09-18  8:33     ` Jan Beulich
2013-09-18  8:37       ` Joanna Rutkowska
2013-09-18  8:50         ` Jan Beulich
     [not found] <mailman.9883.1379496660.32487.xen-devel@lists.xen.org>
2013-09-18 13:49 ` Andres Lagar-Cavilla
2013-09-18 15:42   ` George Dunlap
2013-09-19 10:41     ` Pasi Kärkkäinen
2013-09-19 11:23       ` Sander Eikelenboom
2013-09-19 12:09       ` Jan Beulich
2013-09-20  8:12       ` M A Young
2013-09-19 15:55     ` Stefan Bader

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=5239696B.7070209@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=JBeulich@suse.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.org \
    /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).