[Pkg-rust-maintainers] Bug#1094773: virtiofsd: UID/GID mapping doesn't work anymore

Michael Tokarev mjt at tls.msk.ru
Fri Jan 31 09:40:28 GMT 2025


31.01.2025 03:03, Simon John wrote:
> Package: virtiofsd
> Version: 1.13.0-4
> Severity: important
> 
> Dear Maintainer,
> 
> Since moving to rust, the UID/GID mapping no longer works, despite what the changelog says.
> 
> $ virsh start debian11_pp
> error: Failed to start domain 'debian11_pp'
> error: internal error: process exited while connecting to monitor:
> 2025-01-30T23:37:29.549600Z qemu-system-x86_64: -chardev socket,id=chr-vu-fs0,path=/home/simon/.config/libvirt/qemu/lib/domain-1-debian11_pp/fs0- 
> fs.sock: Failed to connect to
> '/home/simon/.config/libvirt/qemu/lib/domain-1-debian11_pp/fs0-fs.sock':
> Connection refused

What's the output of virtiofsd startup, its error messages?

I don't know how to tell libvirtd to show virtiofsd command line and its
output, unfortunately.

This issue most likely has nothing to do with "uid/gid mappings not working"
as you state.  Here virtiofsd failed to start, and hence qemu can't connect
to it.

Please note virtiofsd definitely works, as demonstrated by the new autopkgtest
(which doesn't work on buildds still, due to other reasons, but works in salsa).

I need the command line used to start virtiofsd, and its (error) messages.

/mjt



More information about the Pkg-rust-maintainers mailing list