xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Eric Shelton <eshelton@pobox.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Anthony PERARD <anthony.perard@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: qemu-upstream stubdom - status?
Date: Mon, 7 Apr 2014 16:50:16 -0400	[thread overview]
Message-ID: <CAPQw5rn7EoDcM4PyfWsETp7YEBAPLNDk5aGTnr7T=E3-BOMsYg@mail.gmail.com> (raw)


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

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.

If I understand this email from Sept 2013 (
http://lists.xen.org/archives/html/xen-devel/2013-09/msg02881.html),
qemu-xen stubdomains might have made it into 4.4 if the schedule had been
slipped a little, suggesting some active effort.  On the other hand, the
same email designated the efforts attached to Anthony and Ian as
"prognosis: ?".  Anthony released a patchset/branch about a year ago, but
that got sidelined in favor of getting Xen on ARM.  However, I did not
identify any more recent patches.

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).

What are the most recent patches or repository for this feature?

Thanks,
Eric

[-- Attachment #1.2: Type: text/html, Size: 1370 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:[~2014-04-07 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 20:50 Eric Shelton [this message]
2014-04-08 10:49 ` qemu-upstream stubdom - status? 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
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='CAPQw5rn7EoDcM4PyfWsETp7YEBAPLNDk5aGTnr7T=E3-BOMsYg@mail.gmail.com' \
    --to=eshelton@pobox.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.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).