From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Upstream QEMU based stubdom and rump kernel Date: Tue, 17 Mar 2015 14:54:09 +0000 Message-ID: <1426604049.18247.260.camel@citrix.com> References: <20150317142907.GD27314@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150317142907.GD27314@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Anthony PERARD , rumpkernel-users@freelists.org, Ian Jackson , Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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.