Popog

Members
  • Posts

    3
  • Joined

  • Last visited

Popog's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. You would have to point your xml to that script as the binary, i.e. <binary path='/usr/libexec/virtiofsd-custom-script' /> where /usr/libexec virtiofsd-custom-script is that one-liner that forwards to the actual virtiofsd. Also you'd need to upgrade to unraid to QEMU 5.2, or at least upgrade the virtiofsd binary, since 5.1 doesn't support that flag. I have not tried any of these proposed workarounds (no idea how to even upgrade QEMU inside of unraid), so who knows if they actually resolve everything, but at least they should get you to the next error.
  2. Trying to create any VM with a simple virtio-fs mount fails Basic XML: <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs'/> <binary path='/usr/libexec/virtiofsd' /> <source dir='/mnt/user/shared'/> <target dir='shared_mount'/> </filesystem> QEMU logs: virtio-fsd logs: stefanha (QEMU person for this feature) said it was most likely because pivot_root doesn't work well under initramfs. QEMU 5.2 might mitigate this issue by adding a flags to use chroot instead (-o sandbox=chroot). Defaulting this behavior would require creating a script like exec /usr/libexec virtiofsd -o sandbox=chroot "$@" stefanha also suggested unraid devs may want to contact virtio-fs developers in #virtio-fs on Freenode IRC or the virtio-fs@redhat.com mailing list (e.g. to see if there is any changes that can be made to unraid to fix pivot_root).