From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
rumpkernel-users@freelists.org,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: Upstream QEMU based stubdom and rump kernel
Date: Tue, 17 Mar 2015 14:54:09 +0000 [thread overview]
Message-ID: <1426604049.18247.260.camel@citrix.com> (raw)
In-Reply-To: <20150317142907.GD27314@zion.uk.xensource.com>
On Tue, 2015-03-17 at 14:29 +0000, Wei Liu wrote:
> 2. The ability to access files in Dom0. That will be used to write to /
> read from QEMU state file.
This requirement is not as broad as you make it sound.
All which is really required is the ability to slurp in or write out a
blob of bytes to a service running in a control domain, not actual
ability to read/write files in dom0 (which would need careful security
consideration!).
For the old qemu-traditional stubdom for example this is implemented as
a pair of console devices (one r/o for restore + one w/o for save) which
are setup by the toolstack at start of day and pre-plumbed into two
temporary files.
Ian.
next prev parent reply other threads:[~2015-03-17 14:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 14:29 Upstream QEMU based stubdom and rump kernel Wei Liu
2015-03-17 14:54 ` Ian Campbell [this message]
2015-03-17 14:57 ` Wei Liu
2015-03-17 15:07 ` Ian Campbell
2015-03-17 15:15 ` Anthony PERARD
2015-03-17 15:23 ` Stefano Stabellini
2015-03-17 15:27 ` Wei Liu
2015-03-17 15:38 ` Ian Campbell
2015-03-18 11:24 ` Martin Lucina
2015-03-18 11:30 ` Ian Campbell
2015-03-18 12:45 ` Stefano Stabellini
2015-03-18 16:46 ` Ian Campbell
2015-03-19 11:16 ` Ian Campbell
2015-03-17 16:06 ` Antti Kantee
2015-03-18 11:22 ` Martin Lucina
2015-03-18 13:22 ` Antti Kantee
2015-03-18 11:20 ` Martin Lucina
2015-03-18 19:05 ` Anil Madhavapeddy
2015-03-18 19:11 ` Martin Lucina
2015-03-18 20:23 ` Antti Kantee
2015-03-18 21:21 ` Anil Madhavapeddy
2015-03-18 22:07 ` Antti Kantee
2015-03-19 8:48 ` Martin Lucina
2015-03-19 9:35 ` Antti Kantee
2015-03-19 12:22 ` Anil Madhavapeddy
2015-03-19 0:19 ` Samuel Thibault
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=1426604049.18247.260.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=rumpkernel-users@freelists.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.