Eduardo Habkost <ehabk...@redhat.com> writes: > On Wed, Oct 21, 2015 at 12:54:23PM +0200, Markus Armbruster wrote: >> Valerio Aimale <vale...@aimale.com> writes: > [...] >> > There's also a similar patch, floating around the internet, the uses >> > shared memory, instead of sockets, as inter-process communication >> > between libvmi and QEMU. I've never used that. >> >> By the time you built a working IPC mechanism on top of shared memory, >> you're often no better off than with AF_LOCAL sockets. >> >> Crazy idea: can we allocate guest memory in a way that support sharing >> it with another process? Eduardo, can -mem-path do such wild things? > > It can't today, but just because it creates a temporary file inside > mem-path and unlinks it immediately after opening a file descriptor. We > could make memory-backend-file also accept a full filename as argument, > or add a mechanism to let QEMU send the open file descriptor to a QMP > client.
Valerio, would an command line option to share guest memory suffice, or does it have to be a monitor command? If the latter, why? Eduardo, I'm not sure writing to guest memory behind TCG's back will work. Do you know? Will it work with KVM?
