You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ incus start bookworm-debusine-worker
Error: Failed to start device "home": Failed to setup virtfs-proxy-helper for device "home": Required binary "virtfs-proxy-helper" couldn't be found
Try `incus info --show-log bookworm-debusine-worker` for more info
Looking in /usr/share/doc/qemu-system-common/changelog.Debian.gz, I see:
qemu (1:9.2.0+ds-1~exp1) experimental; urgency=medium
...
* d/qemu-system-common.*: virtfs-proxy-helper is gone
Try to start an Incus VM that mounts a directory from the host system. (There may be other conditions - I don't know the Incus code here well enough.)
Information to attach
Any relevant kernel output (dmesg): nothing relevant
Container log (incus info NAME --show-log)
Name: bookworm-debusine-worker
Status: STOPPED
Type: virtual-machine
Architecture: x86_64
Created: 2024/03/15 20:32 GMT
Last Used: 2024/10/10 12:19 BST
Error: open /var/log/incus/bookworm-debusine-worker/qemu.log: no such file or directory
Container configuration (incus config show NAME --expanded)
Main daemon log (at /var/log/incus/incusd.log): time="2024-12-23T20:31:35Z" level=warning msg="Unable to use virtio-fs for device, using 9p as a fallback" device=home driver=disk err="Virtiofsd missing" instance=bookworm-debusine-worker project=default
Output of the client with --debug: nothing relevant beyond the "Required binary" message above
Output of the daemon with --debug (alternatively output of incus monitor --pretty while reproducing the issue)
WARNING[2024-12-23T20:39:31Z] Unable to use virtio-fs for device, using 9p as a fallback device=home driver=disk err="Virtiofsd missing" instance=bookworm-debusine-worker project=default
DEBUG [2024-12-23T20:39:31Z] Instance operation lock finished action=start err="Failed to start device \"home\": Failed to setup virtfs-proxy-helper for device \"home\": Required binary \"virtfs-proxy-helper\" couldn't be found" instance=bookworm-debusine-worker project=default reusable=false
I tried installing virtiofsd, which made the "Virtiofsd missing" message go away but otherwise didn't fix the problem.
The text was updated successfully, but these errors were encountered:
Okay, we'll need to look at using that local backend if it supports writing (which last I checked, it didn't...) so then we'd be forced to do virtiofsd which may come with its own problems...
I think we actually use the local backend for basic read-only sharing, for read-write we had to use the proxy, so if that's no longer an option, we'll then have to require the use of virtiofsd in those cases.
@bensmrs let me know if you'd like to look at this one too since you already did some QEMU 9.2 fixes, otherwise I'll get a QEMU 9.2 dev environment up in the next week or so to look at this
Required information
Issue description
Looking in
/usr/share/doc/qemu-system-common/changelog.Debian.gz
, I see:And indeed I see in https://gitlab.com/qemu-project/qemu/-/commit/ed76671888676792493320db53ed773a108cbd45 that this was removed upstream.
Steps to reproduce
Try to start an Incus VM that mounts a directory from the host system. (There may be other conditions - I don't know the Incus code here well enough.)
Information to attach
dmesg
): nothing relevantincus info NAME --show-log
)incus config show NAME --expanded
)time="2024-12-23T20:31:35Z" level=warning msg="Unable to use virtio-fs for device, using 9p as a fallback" device=home driver=disk err="Virtiofsd missing" instance=bookworm-debusine-worker project=default
incus monitor --pretty
while reproducing the issue)I tried installing
virtiofsd
, which made the "Virtiofsd missing" message go away but otherwise didn't fix the problem.The text was updated successfully, but these errors were encountered: