share freezes after a few hours

[Johannes Schlumberger]

Hi,
the problem started after upgrading to noble a few days ago. Starting my vm failed, since virtiofsd could not be found and I installed this package in an attempt to fix it. My vms started again as a result of this.
After a few hours programs trying to access my virtio-share freeze in the guest OS (ubuntu 22.02 at the time). The only way to get out of this is to reboot the guest, which takes forever to shut down and I usually run out of patience and reset it.
I upgraded the guest to noble as well, in an attempt to fix the problem, which made no difference.
This morning I found a seemingly relevant thread upstream https://gitlab.com/virtio-fs/virtiofsd/-/issues/133
People there have had success with using the old qemu virtiofsd instead. I gave that a try and edited my XML vm config to add
    <binary path='/usr/lib/qemu/virtiofsd'/>
to the share section.
It has only been a few hours now, but I have not yet encountered a freeze.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: virtiofsd 1.10.0-1
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Sep 7 12:30:49 2024
InstallationDate: Installed on 2020-12-30 (1347 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=screen
 XDG_RUNTIME_DIR=<set>
SourcePackage: rust-virtiofsd
UpgradeStatus: Upgraded to noble on 2024-09-04 (3 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

[Johannes Schlumberger (spjsschl)]

Some more information.
The share froze for me the same way today with the C-implementation.
It has never frozen for me before upgrading to noble.
The underlying fs is (and always has been) XFS.

In addition, after the freeze I discovered that there were some data inconsistencies.
It seems like the guest assumes a write to disk went through that never makes it to the host. As a result the files end up corrupted.