I had used a Noble guest again even when trying the Jammy host,
so as next theory I thought it might be the guest driver for virtiofs so I
tried a jammy guest - but it also worked.
I've also split the virtiofsd log entries up into phases for you to
better compare:
1. start the guest (= libvirt gets the server ready)
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
2. guest fully boots up (initialize)
fv_queue_set_started: qidx=0 started=1
fv_queue_thread: Start for queue 0 kick_fd 9
fv_queue_set_started: qidx=1 started=1
fv_queue_thread: Start for queue 1 kick_fd 12
3. Mounting and IO
- no log entry
4. shutdown the guest
fv_queue_thread: kill event on queue 0 - quitting
fv_remove_watch: TODO! fd=9
fv_queue_set_started: qidx=1 started=0
fv_queue_thread: kill event on queue 1 - quitting
fv_remove_watch: TODO! fd=12
virtio_loop: Unexpected poll revents 11
virtio_loop: Exit
Do you by any chance have an even older or weirder guest that might
break this in the guest driver initialization phase?
For now this is unclear how to act further, I hope you can outline more
about the guest you use and hopefully find something in comparing your
and my guest setup. Until then marking it incomplete.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083988
Title:
Cannot use virtiofs on Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
