All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: David Lomas <dl3@pale-eds.co.uk>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] Getting help setting up virtiofs guest
Date: Thu, 11 Jun 2020 20:11:54 +0100	[thread overview]
Message-ID: <20200611191154.GI2968@work-vm> (raw)
In-Reply-To: <CALjEBWTnYLtVfJV_KnEv6oqdcWhU-dzoR_pB+C84u798oAw1Vw@mail.gmail.com>

* David Lomas (dl3@pale-eds.co.uk) wrote:
> Apologies if this isn't the correct place for this kind or request.

It's the right place to ask.

> I've been following these instructions to set up host and guest:
> https://virtio-fs.gitlab.io/howto-qemu.html and
> https://libvirt.org/kbase/virtiofs.html
> 
> On the host, I've built the latest version of libvirt (6.4.0) and qemu
> (5.0.0), and added sections to the domain definition. All appears well (no
> errors at least). This is the relevant section:
> 
>     <filesystem type='mount' accessmode='passthrough'>
>       <driver type='virtiofs'/>
>       <binary path='/usr/libexec/virtiofsd'/>
>       <source dir='/fast_data/test'/>
>       <target dir='test'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x06'
> function='0x0'/>
>     </filesystem>

I think that's OK.

> On the guest, I've build the kernel (4.19.28), booted it, and confirmed
> virtio_fs.ko is a built-in module.

Where did you get that kernel?  It sounds rather old;  the main part of
virtiofs is now in the upstream kernel; so if your distro has a recent
5.x kernel, you can just use it.

> But on running mount -t virtio_fs test /mnt/test/ I get the following error:
> 
> mount: /mnt/test: wrong fs type, bad option, bad superblock on qube-server,
> missing codepage or helper program, or other error.
> 
> Note both those web pages above suggest using mount -t virtiofs, but that
> gives unknown filesystem type 'virtiofs'

It changed in the newer kernels to the 'virtiofs'.

> I'm at a loss to find more detailed information on how to configure
> this—are there other resources online, or can anyone suggest what to try
> next?

I suspect you're suffering from the older kernel here.  Try a nice
shiny new one.

Dave

> Thanks!

> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs

--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  reply	other threads:[~2020-06-11 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 19:01 [Virtio-fs] Getting help setting up virtiofs guest David Lomas
2020-06-11 19:11 ` Dr. David Alan Gilbert [this message]
2020-06-12 11:42   ` David Lomas
2020-06-15  9:55     ` Dr. David Alan Gilbert
2020-06-15 10:19       ` Dr. David Alan Gilbert

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=20200611191154.GI2968@work-vm \
    --to=dgilbert@redhat.com \
    --cc=dl3@pale-eds.co.uk \
    --cc=virtio-fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.