From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Upstream QEMU based stubdom and rump kernel Date: Thu, 19 Mar 2015 11:16:48 +0000 Message-ID: <1426763808.610.36.camel@citrix.com> References: <20150317142907.GD27314@zion.uk.xensource.com> <20150317151517.GI1345@perard.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150317151517.GI1345@perard.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: Anthony PERARD Cc: Ian Jackson , rumpkernel-users@freelists.org, Wei Liu , Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, 2015-03-17 at 15:15 +0000, Anthony PERARD wrote: > On Tue, Mar 17, 2015 at 02:29:07PM +0000, Wei Liu wrote: > > I've now successfully built QEMU upstream with rump kernel. However to > > make it fully functional as a stubdom, there are some missing pieces to > > be added in. > > > > 1. The ability to access QMP socket (a unix socket) from Dom0. That > > will be used to issue command to QEMU. > > The QMP "socket" does not needs to be a unix socket. It can be any of > those (from qemu --help): > Character device options: > -chardev null,id=id[,mux=on|off] How much flexibility/modularity is there on the qemu side for adding new chardev types? Could we for example add "-chardev vchan,path=path" without too much trouble? > To save a QEMU state (write), we do use a filename. But I guest we could > expand the QMP command (xen-save-devices-state) to use something else, if > it's easier. Like, perhaps, an arbitrary chardev? Ian.