Comment 7 for bug 1912214

Next I was trying the same LXD setup that failed before on a different host (to check if it would be reproducible).

Current LXD setup (Failing):
- LXD is at 4.10 (most recent on latest/stable channel)
- Kernel 5.4.0-60

Current Bare-Metal setup (working)
- Kernel 5.10.6-051006

New LXD try #0 - LXD on other system (Failing)
- same system that has the working bare metal
- Same setup as the other LXD based tests
- Kernel 5.10.6-051006
=> Same issue, the access is blocked even if I add the paths as local override

New LXD try #1 - older hirsute kernel (failing)
- Same setup as the other tests with LXD
- Kernel 5.8.0-36

New BareMetal #1 - older hirsute kernel (working):
- Kernel 5.8.0-36

New LXD try #2 - Focal kernel (failing)
- Same setup as the other tests with LXD
- Kernel 5.4.0-54

New BareMetal #2 - Focal kernel (working):
- Kernel 5.4.0-54

New LXD try #3 - recheck on 5.10 (failing)
- Same setup as the other tests with LXD
- Kernel 5.10.6-051006

New LXD try #4 - recheck on 5.8 (failing now)
- Same setup as the other tests with LXD
- Kernel 5.8.0-36

New LXD try #5 - Other 5.10 this time from H-proposed (TBD)
- Same setup as the other tests with LXD
- The former 5.10 I tried was a mainline build (https://kernel.ubuntu.com/~kernel-ppa/mainline/)
- Kernel 5.10.6-051006

So there is no new kernel that makes it work.
And the problem should be reproducible in many places.

I'll add the steps to drive KVM in a container to the description to ease repro