Your message dated Thu, 8 Jun 2023 15:25:03 +0300
with message-id <[email protected]>
and subject line Re: Bug#1017394: qemu-system-common: virtiofsd aborts with
error: fv_panic: libvhost-user: Invalid vring_addr message
has caused the Debian Bug report #1017394,
regarding qemu-system-common: virtiofsd aborts with error: fv_panic:
libvhost-user: Invalid vring_addr message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1017394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017394
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-common
Version: 1:7.0+dfsg-7
Severity: normal
# /usr/lib/qemu/virtiofsd --socket-path=/vmstore/sock/doc -o
source=/usr/share/doc -o cache=always --socket-group=kvm
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_panic: libvhost-user: Invalid vring_addr message
#
I am trying out virtiofs, I run the daemon with the above options and run kvm
with the below
options and when I try to mount the mountiofs filesystem it aborts. I am not
certain that I am
doing it correctly (this is my first attempt and I have never had it work), but
I am certain that
it's not supposed to just abort with such an error.
kvm -cpu host -object rng-random,filename=/dev/urandom,id=rng0 -device
virtio-rng-pci,rng=rng0 -drive format=raw,file=/vmstore/exectl,if=virtio -drive
format=raw,file=/vmswap/exectl,if=virtio -smp 4 -m 8000 -kernel
/vmstore/kern/vmlinuz-5.19.0 -initrd /vmstore/kern/initrd-5.19.0 -append
net.ifnames=0 noresume lsm=integrity ima_hash=sha256 ima_policy=secure_boot
ima_appraise=fix evm=fix root=/dev/vda ro -device
virtio-net-pci,netdev=net0,romfile=,mac=02:00:00:00:02:02 -netdev
tap,id=net0,helper=/usr/lib/qemu/qemu-bridge-helper,br=br0 -display curses
-chardev socket,id=doc,path=/vmstore/sock/doc -device
vhost-user-fs-pci,queue-size=1024,chardev=doc,tag=doc
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-15-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default
Versions of packages qemu-system-common depends on:
ii libaio1 0.3.113-2
ii libasound2 1.2.7.2-1
ii libbrlapi0.8 6.5-3+b1
ii libc6 2.33-8
ii libcacard0 1:2.8.0-3
ii libcap-ng0 0.8.3-1+b1
ii libepoxy0 1.5.10-1
ii libfuse3-3 3.11.0-1
ii libgbm1 22.2.0~rc1-1
ii libglib2.0-0 2.72.3-1
ii libgnutls30 3.7.7-2
ii libncursesw6 6.3+20220423-2
ii libnettle8 3.7.3-1
ii libpixman-1-0 0.40.0-1
ii libseccomp2 2.5.4-1+b1
ii libspice-server1 0.15.0-4
ii libtinfo6 6.3+20220423-2
ii liburing2 2.2-1
ii libusb-1.0-0 2:1.0.26-1
ii libusbredirparser1 0.11.0-2
ii libzstd1 1.5.2+dfsg-1
ii zlib1g 1:1.2.11.dfsg-4
qemu-system-common recommends no packages.
qemu-system-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:8.0+dfsg-1
On Mon, 15 Aug 2022 22:01:42 +1000 Russell Coker <[email protected]> wrote:
Package: qemu-system-common
Version: 1:7.0+dfsg-7
Severity: normal
# /usr/lib/qemu/virtiofsd --socket-path=/vmstore/sock/doc -o
source=/usr/share/doc -o cache=always --socket-group=kvm
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_panic: libvhost-user: Invalid vring_addr message
#
I am trying out virtiofs, I run the daemon with the above options and run kvm
with the below
options and when I try to mount the mountiofs filesystem it aborts. I am not
certain that I am
doing it correctly (this is my first attempt and I have never had it work), but
I am certain that
it's not supposed to just abort with such an error.
...
With 8.0, qemu upstream does not ship this C-language implementation of
virtiofsd anymore,
a rust implementation (packaged separately) is used instead.
So it looks like this bug report can now be closed.
Thanks,
/mjt
--- End Message ---
