> On Oct 04, 2016, at 10:50, Marc-André Lureau <marcandre.lur...@gmail.com> > wrote: > > What about having a single config parameter as a place to put all vhost logs > for all drives for a single instance ? Remove the memfd implementation with > all the memfd shared_memory option ? Replace it with a > open+unlink+ftruncate+mmap approach only. > > > I fail to see your point, memfd is superior to open+unlink and has other > advantages with sealing etc.
I was just summarising needs based on previous statement from Daniel: > This makes me wonder about the memfd_create() code path too - we'll > again not want that external process to be granted access to arbitrary > FDs of QEMU's and I'm not sure of a way to get the memfd FD to have > a specific label. So I think it is possible that when using libvirt > we'll want the ability to tell QEMU to *always* use an explicit file > in a path libvirt specifies, and never use memfd even if available. > > Regards, > Daniel
