Tom Parrott

Ah no, it wont actually because of https://github.com/canonical/lxd/blob/stable-5.0/lxd/device/disk.go#L936 I think. We need to see about using the same technique and passing a file handle to QEMU.

@hamistao Don't worry about this line: ``` qemu-system-x86_64:/var/snap/lxd/common/lxd/logs/stg-ps6-small2-3-166d3e5f-ba4f-4cd0-817e-1ba1994e8c8d/qemu.conf:273: warning: '-fsdev proxy' and '-virtfs proxy' are deprecated, use 'local' instead of 'proxy, or consider deploying virtiofsd as alternative to 9p ```...

One approach could be to open a file handle and then pass it as a file path using `/proc/self/fd/`

Took a look at this and found this in `/var/snap/lxd/common/lxd/logs/c1/lxc.log` after setting `sudo snap set lxd daemon.debug=true; sudo systemctl reload snap.lxd.daemon`: ``` lxc c1 20240719091404.652 DEBUG conf - ../src/src/lxc/conf.c:run_buffer:311 -...

@simondeziel @mihalicyn btw ive confirmed this is also an issue going from 5.0/stable to 5.0/edge so it'll need to be sorted before we put out 5.0.4 with core22.

Yep, a good chance, its on my list as a high priority, we know what the issue is and have a plan to address it.

Working on a fix here https://github.com/canonical/lxd/pull/14182

The issue here is that between LXD 5.0.x and LXD 5.21.0 onwards the base snap version has changed from core20 to core22. This has involved changing the glibc version and...

This is a problem because we are also planning to change the base snap of LXD 5.0.x to core22 which would then introduce the same issue for a point release...

Good idea, I'll try that. I might just remove the callhook conditional entirely and force the same set of LD_LIBRARY_PATHs for all invocations. I prefer that idea to overmounting as...