From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Pedro Serrano <kpiq@gmx.us>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org
Subject: Re: unknown fs driver type 'virtiofs'
Date: Mon, 24 Aug 2020 18:45:21 +0100 [thread overview]
Message-ID: <20200824174521.GA2688@work-vm> (raw)
In-Reply-To: <trinity-3bf6c693-675f-4587-a673-717b058ceb06-1598236839217@3c-app-mailcom-bs08>
* Pedro Serrano (kpiq@gmx.us) wrote:
> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><pre>Folks
>
> The instructions posted on <a href="http://blog.vmsplice.net/2020/04/virtio-fs-has-landed-in-qemu-50.html" target="_blank">http://blog.vmsplice.net/2020/04/virtio-fs-has-landed-in-qemu-50.html</a> are simple and I followed them.
>
> I've updated my Debian Buster QEMU and LIBVIRT packages to all the newest buster-backports versions, and am running on:
>
> Linux ps01ubx 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64 GNU/Linux
>
> lsmod|grep virtio
> virtiofs 32768 0
> virtio_ring 36864 1 virtiofs
> virtio 16384 1 virtiofs
> fuse 139264 4 virtiofs
>
> dpkg -l gir1.2-libvirt-glib-1.0:amd64 ipxe-qemu libvirglrenderer0:amd64 libvirt-clients libvirt-daemon libvirt-daemon-system libvirt-glib-1.0-0:amd64 libvirt0:amd64 python3-libvirt qemu qemu-block-extra qemu-system-common qemu-system-data qemu-system-gui:amd64 qemu-system-x86 qemu-utils
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture Desc
> +++-=============================-============================-============-====
> ii gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 amd64 GObj
> ii ipxe-qemu 1.0.0+git-20190125.36a4c85-1 all PXE
> ii libvirglrenderer0:amd64 0.7.0-2 amd64 virt
> ii libvirt-clients 5.0.0-4+deb10u1 amd64 Prog
> ii libvirt-daemon 5.0.0-4+deb10u1 amd64 Virt
> ii libvirt-daemon-system 5.0.0-4+deb10u1 amd64 Libv
> ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64 libv
> ii libvirt0:amd64 5.0.0-4+deb10u1 amd64 libr
> ii python3-libvirt 5.0.0-1 amd64 libv
> ii qemu 1:5.0-14~bpo10+1 amd64 fast
> ii qemu-block-extra 1:5.0-14~bpo10+1 amd64 extr
> ii qemu-system-common 1:5.0-14~bpo10+1 amd64 QEMU
> ii qemu-system-data 1:5.0-14~bpo10+1 all QEMU
> ii qemu-system-gui:amd64 1:5.0-14~bpo10+1 amd64 QEMU
> ii qemu-system-x86 1:5.0-14~bpo10+1 amd64 QEMU
> ii qemu-utils 1:5.0-14~bpo10+1 amd64 QEMU
>
> Whenever I add a filesystem to the vm xml (virsh edit vm) virt-manager spits out an error message. Because virt-manager doesn't have a "virtiofs" line in the drop-down choices I first choose "PATH" and then try to change the XML.
>
> <filesystem type='mount' accessmode='passthrough'>
> <driver type='virtiofs'/></pre>
>
>
>
> The result is similar, whether I use virt-manager or virsh edit vm:
>
I think your libvirt is too old; my reckoning is it went in v6.1.0 (or
was it 6.2.0?)
> virtio-manager replies: unknown fs driver type 'virtiofs'
>
> virsh edit vm does not let me save the file. It replies:
> error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng<br/>
> Extra element devices in interleave<br/>
> Element domain failed to validate content
>
> Failed. Try again? [y,n,i,f,?]:
>
>
> What am I doing wrong?
You're also using HTML mail without plaintext!
Dave
> Regards
>
> Pedro Serrano
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
parent reply other threads:[~2020-08-24 17:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <trinity-3bf6c693-675f-4587-a673-717b058ceb06-1598236839217@3c-app-mailcom-bs08>]
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=20200824174521.GA2688@work-vm \
--to=dgilbert@redhat.com \
--cc=kpiq@gmx.us \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).