xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	"Jan Beulich" <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.1.x security support
Date: Tue, 17 Sep 2013 21:46:39 +0100	[thread overview]
Message-ID: <1379450799.11304.205.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <5238B3AA.3090805@invisiblethingslab.com>

On Tue, 2013-09-17 at 21:55 +0200, Joanna Rutkowska wrote:
> On 09/17/13 21:18, Ian Campbell wrote:
> My point was that you should be adding very few features or none at all,
> keep the hypervisor as simple as possible, do not change the management
> stack all the time, etc.

I think "all the time" is a gross exaggeration TBH.

>  Otherwise it makes it difficult for other
> projects/products who use Xen to catch up. What version does Xen Client
> use, BTW?

I don't know. I'm not sure why you think I would.

> Really, who needs nested virtualization, or XSM -- these are of pure
> academic interest and only make the hypervisor unnecessary bloated, IMO.

Well, that's *your* opinion.

BTW if you want a version of Xen without those things to continue to be
supported then you are very welcome to volunteer to take over
maintenance of the 4.0 (or any, I don't know how far back you'd need to
go to predate XSM for example) stable branch once xen.org support runs
out.

> Why not keep everything that is not "core" as separate repos/projects,
> conditionally compiled/linked with the core hypervisor?

Because that would be an unmanageable nightmare for everyone involved?

> When a hypervisor gets too complex it suddenly looses all its appeal
> over a traditional kernel, doesn't it?

TBH I think you are either focused on only your own needs/requirements
or maybe you are just trolling, in which case I sadly appear to have
fallen for it. In any case I don't think I'll bother reading the rest of
this thread.

Ian.

  parent reply	other threads:[~2013-09-17 20:46 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 [this message]
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
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=1379450799.11304.205.camel@hastur.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=joanna@invisiblethingslab.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).