In the guest log that libvirt creates you'd find how it started virtiofsd for you, for example in my working case:
Noble: $ sudo grep virtiofs /var/log/libvirt/qemu/j-vfs.log 2024-10-10 06:19:17.362+0000: Starting external device: virtiofsd /usr/libexec/virtiofsd --fd=34 -o source=/var/guests/j-vfs Jammy: $ sudo grep virtiofsd /var/log/libvirt/qemu/j-guest.log 2024-10-09 08:52:11.417+0000: Starting external device: virtiofsd /usr/lib/qemu/virtiofsd --fd=34 -o source=/var/guests/j-guest Is that simple call with "binary + pre setup fd + source-path" the same you see in your log? Or vice versa, if we want to make the command libvirt uses more similar to the manual call you had, we can add options to the XML. For example adding `<cache mode='always'/>` in the XML makes it add `,cache=always` to the options. A socket='' config in the guest XML is only meant for externally launched virtiofsd instances, so setting that isn't helpful. We might also check if you use the "normal" virtiofsd that comes with the distro, can you check if these report the same for you? Noble: $ dpkg -S /usr/libexec/virtiofsd virtiofsd: /usr/libexec/virtiofsd $ dpkg -l virtiofsd ... ii virtiofsd 1.10.0-1 amd64 Virtio-fs vhost-user device daemon $ dpkg --verify virtiofsd < no output here > Jammy: $ dpkg -S /usr/lib/qemu/virtiofsd qemu-system-common: /usr/lib/qemu/virtiofsd $ dpkg -l qemu-system-common ... ii qemu-system-common 1:6.2+dfsg-2ubuntu6.22 amd64 QEMU full system emulation binaries (common files) $ dpkg --verify qemu-system-common < no output here > Your initial report already states you have qemu-system-common 1:6.2+dfsg-2ubuntu6.22, but maybe things got damaged or overwritten - or libvirt detects a different virtiofsd (seen in the logs) Finally I wondered (thanks for your full XML) if it could it be something about access permissions since you configure it to use /home/rbeldin/Downloads. I tried <source dir='/home/paelzer/Downloads/'/> here but that works just as much. P.S. Because this slightly changed between Jammy and Noble I try to provide both examples each time for anyone else that might come by and compare their setup :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083988 Title: Cannot use virtiofs on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
