Unable to set XATTR trusted.libvirt.security.dac Operation not supported
Running with Kernel 6.1.8 QEMU 7.1 libvirt 8.7 setting remeber_owner = 0 resolves the issue but was working ok on kernel 6.0.x. root@computenode:~# cat /etc/libvirt/qemu.conf | grep reme # Whether libvirt should remember and restore the original remember_owner = 0 root@computenode:~# Any known issues for this, is it likely to be QEMU/KVM?
On 2/2/23 20:05, Simon Fairweather wrote:
Running with Kernel 6.1.8
QEMU 7.1 libvirt 8.7
setting remeber_owner = 0 resolves the issue but was working ok on kernel 6.0.x.
root@computenode:~# cat /etc/libvirt/qemu.conf | grep reme # Whether libvirt should remember and restore the original remember_owner = 0 root@computenode:~#
Any known issues for this, is it likely to be QEMU/KVM?
So is there a failure you're seeing (e.g. a domain unable to start) or is this just a warning printed into logs? Can you shed more light into what path is libvirt unable to set XATTRs on and what's the underlying filesystem? Michal
Thanks Michal, following your suggestion on FS It looks like a fuse 3.13.0 issue, if I use drive mount point it works. Should have checked this first. Error was on VM start and would not let it start. Regards Simon. On Mon, Feb 6, 2023 at 9:20 AM Michal Prívozník <mprivozn@redhat.com> wrote:
On 2/2/23 20:05, Simon Fairweather wrote:
Running with Kernel 6.1.8
QEMU 7.1 libvirt 8.7
setting remeber_owner = 0 resolves the issue but was working ok on kernel 6.0.x.
root@computenode:~# cat /etc/libvirt/qemu.conf | grep reme # Whether libvirt should remember and restore the original remember_owner = 0 root@computenode:~#
Any known issues for this, is it likely to be QEMU/KVM?
So is there a failure you're seeing (e.g. a domain unable to start) or is this just a warning printed into logs?
Can you shed more light into what path is libvirt unable to set XATTRs on and what's the underlying filesystem?
Michal
On 2/6/23 10:49, Simon Fairweather wrote:
Thanks Michal, following your suggestion on FS It looks like a fuse 3.13.0 issue, if I use drive mount point it works. Should have checked this first.
No problem. Do you have a link to a bug report perhaps? I'd like to check to see if it's worth changing libvirt so that it does not tackle this bug. What worries me is that firstly, libvirt tries to read XATTRs and upon seeing ENOTSUP it doesn't proceed to setting XATTRs on given file. Therefore, reading XATTRs must have succeeded but setting them failed. Was this a read-only FS perhaps? Michal
Issue report is here https://github.com/libfuse/libfuse/issues/730 On Mon, 6 Feb 2023, 10:49 Michal Prívozník, <mprivozn@redhat.com> wrote:
On 2/6/23 10:49, Simon Fairweather wrote:
Thanks Michal, following your suggestion on FS It looks like a fuse 3.13.0 issue, if I use drive mount point it works. Should have checked this first.
No problem. Do you have a link to a bug report perhaps? I'd like to check to see if it's worth changing libvirt so that it does not tackle this bug.
What worries me is that firstly, libvirt tries to read XATTRs and upon seeing ENOTSUP it doesn't proceed to setting XATTRs on given file. Therefore, reading XATTRs must have succeeded but setting them failed. Was this a read-only FS perhaps?
Michal
participants (2)
-
Michal Prívozník -
Simon Fairweather