dmesg spammed by virtui-fs and 9pnet-virtio messages

[Colin Ian King]

Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel messages after boot (running instances in a VM using virt-manager)

uname -a
Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

[ 30.638354] virtio-fs: tag <config> not found
[ 30.642316] 9pnet_virtio: no channels available for device config
[ 35.897615] virtio-fs: tag <config> not found
[ 35.901568] 9pnet_virtio: no channels available for device config
[ 41.141860] virtio-fs: tag <config> not found
[ 41.145513] 9pnet_virtio: no channels available for device config
[ 46.382040] virtio-fs: tag <config> not found
[ 46.386141] 9pnet_virtio: no channels available for device config
[ 51.632229] virtio-fs: tag <config> not found
[ 51.635727] 9pnet_virtio: no channels available for device config

These are annoying when logging in via the console.

[Andrea Righi (arighi)]

I don't see these messages with the latest Noble using the kernel from the proposed pocket (6.8.0-11-generic). Can you also give it a try (if you can)?

Hopefully we'll be able to promote a 6.8 in release soon, we are currently blocked by a glibc regression (that doesn't seem to be a kernel regression). If we can unblock/hint this one (hopefully this week, or worst case next week) we'll have a new 6.8 in release.

[Colin Ian King (colin-king)]

cking@noble-amd64:~$ uname -a
Linux noble-amd64 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

[ 9.551968] virtio-fs: tag <config> not found
[ 9.555352] 9pnet_virtio: no channels available for device config
[ 14.850014] virtio-fs: tag <config> not found
[ 14.854959] 9pnet_virtio: no channels available for device config
[ 18.302513] systemd-journald[451]: /var/log/journal/c8f7ec498f904c46b99f25f051792ec0/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[ 20.173092] virtio-fs: tag <config> not found
[ 20.176498] 9pnet_virtio: no channels available for device config
[ 25.470406] virtio-fs: tag <config> not found
[ 25.475163] 9pnet_virtio: no channels available for device config
[ 30.690179] virtio-fs: tag <config> not found
[ 30.695584] 9pnet_virtio: no channels available for device config
[ 35.947869] virtio-fs: tag <config> not found
[ 35.951397] 9pnet_virtio: no channels available for device config
[ 41.190386] virtio-fs: tag <config> not found
[ 41.195323] 9pnet_virtio: no channels available for device config
[ 46.437815] virtio-fs: tag <config> not found
[ 46.441903] 9pnet_virtio: no channels available for device config
[ 51.700719] virtio-fs: tag <config> not found
[ 51.704995] 9pnet_virtio: no channels available for device config

..but it stops now after ~52 seconds after boot. Anyhow, these are unusual new messages from the previous mantic kernel.

[Andrea Righi (arighi)]

I haven't been able to reproduce this on my PC yet... Looking at the error, especially the virtio-fs part, I'm wondering if you're missing virtiofsd in your host. Can you try to `apt install virtiofsd` (if you don't have it installed already)?

[Colin Ian King (colin-king)]

Good idea,

I've installed this on my host and it's still occurring on various VM architectures (x86-64, ppc64el, s390x, ect). My host is noble and up to date with updates.

[Colin Ian King (colin-king)]

Does not occur on pre-noble VMs, e.g. fine with mantic through to trusty on all my VMs on the same host.

[Dustin Fields (stormycloud)]

I also have this issue the machines that have this issue have all been upgraded from jammy. This happens both on virtual servers and bare metal installs.

[Russell Jones (russell-jones-oxphys)]

Is this related to https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814 ?