Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Idea: fuse-kvm filesystem
Date: Thu, 10 May 2012 15:55:17 +0300	[thread overview]
Message-ID: <4FABBAB5.9010506@redhat.com> (raw)
In-Reply-To: <20120510123505.GM15276@amd.home.annexia.org>

On 05/10/2012 03:35 PM, Richard W.M. Jones wrote:
> On Thu, May 10, 2012 at 03:29:54PM +0300, Avi Kivity wrote:
> > Currently when you mount a filesystem, you face two issues:
> > - you have to be root
> > - if the media is untrusted, it can exploit your kernel
> > 
> > With kvm and fuse, we can have a virtualized kernel mount the
> > filesystem, and re-export to the host, which mounts it using a fuse
> > interface.  This solves both problems, at the expense of speed and
> > simplicity.  In theory this can be used for mounting untrusted USB
> > sticks (perhaps only for the less well tested filesystems).
>
> I guess you CC'd me so I could point out guestmount :-?
>
>   http://libguestfs.org/guestmount.1.html

Is there a feature that libguestfs doesn't have?

Anyway I tried it out and it seems to work really well.

> guestmount does the above already, and you can point it directly at
> USB sticks, hard drives and the like, although most people use it for
> mounting VM filesystems on the host.
>
> On my local machine I'm a member of the "disk" group so I can do all
> this as non-root:
>
>   $ guestmount --ro -a /dev/vg_pin/F16x64 -i /tmp/mnt
>   $ cat /tmp/mnt/etc/redhat-release 
>   Fedora release 16 (Verne)
>   $ ls /tmp/mnt
>   bin   dev  home  lib64       media  opt   root  sbin     srv  tmp  var
>   boot  etc  lib   lost+found  mnt    proc  run   selinux  sys  usr
>
> One problem you'll find is that FUSE is pretty slow.  I recommend if
> you're looking for performance that you use the libguestfs API calls
> directly instead of POSIX-over-FUSE.

Yes, 'guestmount' consumes a fair bit of cpu.  But it probably doesn't
matter for USB sticks.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-05-10 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 12:29 Idea: fuse-kvm filesystem Avi Kivity
2012-05-10 12:35 ` Richard W.M. Jones
2012-05-10 12:55   ` Avi Kivity [this message]
2012-05-10 12:37 ` [Qemu-devel] " Alex Bradbury
2012-05-10 12:56   ` Avi Kivity
2012-05-10 14:09 ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FABBAB5.9010506@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox