xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Antti Kantee <pooka@iki.fi>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Eric Shelton <eshelton@pobox.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Justin Cormack <justin@specialbusservice.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: qemu-upstream stubdom - status?
Date: Tue, 08 Apr 2014 11:33:37 +0000	[thread overview]
Message-ID: <5343DE91.5070109@iki.fi> (raw)
In-Reply-To: <21315.54351.255895.917360@mariner.uk.xensource.com>

On 08/04/14 10:49, Ian Jackson wrote:
> Eric Shelton writes ("qemu-upstream stubdom - status?"):
>> Where does this feature stand currently?  It pops up under a couple
>> of names and proposed implementations (e.g., "qemu-xen stubdomains",
>> "qemu-upstream stubdom, Linux", and "qemu-upstream stubdom, BSD
>> libc"), so it seems likely I missed something.
>
> Hi.  I made a start on bsd libc + minios last release cycle but I
> think this has now been overtaken by the rump kernels work by Antti
> Kantee.  See https://github.com/rumpkernel/wiki/wiki etc.
>
>> It remains appealing to make use of the more recent developments in
>> qemu-upstream, but with the isolation provided by a stubdomain.  The
>> many improvements made in teasing driver domains out of dom0
>> strengthen this appeal (for example, using OpenSolaris as a
>> ZFS-based storage domain).
>
> Yes.
>
>> What are the most recent patches or repository for this feature?
>
> I've just started looking at the rump kernels with a view to
> (eventually) trying to get qemu-upstream working but I don't have
> anything I can show you yet.

Last time we discussed this (ca. FOSDEM-time), I put up a page to list 
the issues with the hopes of a TODO-list making it easy to just tick 
items off quickly.  Wishful thinking.  I probably also forgot to send 
the URL to you.  Anyway, I updated the content now, here's the URL:

http://wiki.rumpkernel.org/Info:-Remaining-issues-for-%22OS-less%22-rump-kernels

I think Justin Cormack (also cc'd) has something yet unpublished for the 
build issue with some form of "compiler triplet".

  reply	other threads:[~2014-04-08 11:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 20:50 qemu-upstream stubdom - status? Eric Shelton
2014-04-08 10:49 ` George Dunlap
2014-04-08 11:26   ` Anthony PERARD
2015-01-08 16:39     ` Eric Shelton
2014-04-08 10:49 ` Ian Jackson
2014-04-08 11:33   ` Antti Kantee [this message]
2014-04-08 17:03     ` Ian Jackson
2014-04-08 17:04       ` Justin Cormack
2014-04-08 17:47         ` Ian Jackson
2014-04-08 17:13       ` Justin Cormack
2014-04-08 17:47         ` Ian Jackson
2014-04-08 22:54           ` Antti Kantee

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=5343DE91.5070109@iki.fi \
    --to=pooka@iki.fi \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=eshelton@pobox.com \
    --cc=justin@specialbusservice.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).