Virtiofsd 1.9.0 could not be used with libvirt qemu machines
Description:
After upgrading to virtiofsd from 1.8.0 to 1.9.0, I found that my VMs inside libvirt could no longer use virtio file sharing: Windows VM no longer shows corresponding volume and Linux VM just hangs when accessing relevant mountpoints.
I found that virtiofsd process spawns when just booting VM, but then exits after logining in Windows/Linux.
Additional info:
- package version(s): 1.9.0-1
- config and/or log files:
/var/log/libvirt/qemu/xxx-virtiofsd.log
:
[2023-12-26T09:38:04Z INFO virtiofsd] Waiting for vhost-user socket connection...
[2023-12-26T09:38:04Z INFO virtiofsd] Client connected, servicing requests
[2023-12-26T09:38:11Z ERROR virtiofsd] Waiting for daemon failed: HandleRequest(InvalidMessage)
[2023-12-26T10:02:43Z WARN virtiofsd] Use of deprecated option format '-o': Please specify options without it (e.g., '--cache auto' instead of '-o cache=auto')
[2023-12-26T10:02:43Z INFO virtiofsd] Waiting for vhost-user socket connection...
[2023-12-26T10:02:43Z INFO virtiofsd] Client connected, servicing requests
[2023-12-26T10:02:49Z ERROR virtiofsd] Waiting for daemon failed: HandleRequest(InvalidMessage)
[2023-12-26T10:06:00Z WARN virtiofsd] Use of deprecated option format '-o': Please specify options without it (e.g., '--cache auto' instead of '-o cache=auto')
[2023-12-26T10:06:00Z INFO virtiofsd] Waiting for vhost-user socket connection...
[2023-12-26T10:06:01Z INFO virtiofsd] Client connected, servicing requests
[2023-12-26T10:06:10Z ERROR virtiofsd] Waiting for daemon failed: HandleRequest(InvalidMessage)
[2023-12-26T10:09:02Z WARN virtiofsd] Use of deprecated option format '-o': Please specify options without it (e.g., '--cache auto' instead of '-o cache=auto')
- link to upstream bug report, if any:
https://gitlab.com/virtio-fs/virtiofsd/-/issues/140 seems related.
Steps to reproduce:
- Upgrading virtiofsd to 1.9.0-1
- Setup file sharing in VM like this:
XML config:
<filesystem type="mount" accessmode="passthrough">
<driver type="virtiofs" queue="1024"/>
<source dir="/home/user/Sharing"/>
<target dir="Sharing"/>
<address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/>
</filesystem>
- Boot, and no virtiofsd process is alive after VM system boots up (system needs to be configured to mount virtiofs though).