Folks

The instructions posted on http://blog.vmsplice.net/2020/04/virtio-fs-has-landed-in-qemu-50.html 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'/>
 
The result is similar, whether I use virt-manager or virsh edit vm:
 
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
Extra element devices in interleave
Element domain failed to validate content
Failed. Try again? [y,n,i,f,?]: 
 
What am I doing wrong?
 
Regards
 
Pedro Serrano
 
 

Reply via email to