Re: [Qemu-devel] [PATCH 1/2] Dump: introduce a Filesystem in Userspace

[Daniel P. Berrange]

On Mon, May 09, 2016 at 09:52:28AM -0600, Eric Blake wrote:
> On 05/07/2016 05:32 PM, Nan Li wrote:
> > When running the command "dump-guest-memory", we usually need a large space
> > of storage to save the dumpfile into disk. It costs not only much time to
> > save a file in some of hard disks, but also costs limited storage in host.
> > In order to reduce the saving time and make it convenient for users to dump
> > the guest memory, we introduce a Filesystem in Userspace (FUSE) to save the
> > dump file in RAM. It is selectable in the configure file, adding a compiling
> > of package "fuse-devel". It doesn't change the way of dumping guest memory.
> 
> Why introduce FUSE? Can we reuse NBD instead?

The commit message talks of letting QEMU dump to RAM avoiding disk I/O.
IOW, it seems like it could just dump to any tmpfs directory.

I'm not really seeing a compelling reason why QEMU needs to mount a fuse
filesystem itself - whatever app is using QEMU could handle mounting of
fs without QEMU's involvement at all.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|