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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
