Issue report is here https://github.com/libfuse/libfuse/issues/730
On Mon, 6 Feb 2023, 10:49 Michal Prívozník, 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
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
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 wrote:
> On 2/2/23 20:05,
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
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
