On Wed, Mar 20, 2024 at 10:19:11 +0100, Andrea Bolognani wrote: > As explained in the comment, this can help in scenarios where > a shared filesystem can't be detected as such by libvirt, by > giving the admin the opportunity to provide this information > manually. > > Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> > --- > src/qemu/libvirtd_qemu.aug | 3 +++ > src/qemu/qemu.conf.in | 17 +++++++++++++++++ > src/qemu/qemu_conf.c | 17 +++++++++++++++++ > src/qemu/qemu_conf.h | 2 ++ > src/qemu/test_libvirtd_qemu.aug.in | 5 +++++ > 5 files changed, 44 insertions(+) [...] > diff --git a/src/qemu/qemu.conf.in b/src/qemu/qemu.conf.in > index f406df8749..db42448239 100644 > --- a/src/qemu/qemu.conf.in > +++ b/src/qemu/qemu.conf.in > @@ -986,3 +986,20 @@ > # note that the default might change in future releases. > # > #storage_use_nbdkit = @USE_NBDKIT_DEFAULT@ > + > +# libvirt will normally prevent migration if the storage backing the VM is not > +# on a shared filesystems. Sometimes, however, the storage *is* shared despite > +# not being detected as such: for example, this is the case when one of the > +# hosts involved in the migration is exporting its local storage to the other > +# one via NFS. > +# > +# Any directory listed here will be assumed to live on a shared filesystem, > +# making migration possible in scenarios such as the one described above. > +# > +# If you need this feature, you probably want to set remember_owner=0 too. Could you please elaborate why you'd want to disable owner remembering? With remote filesystems this works so I expect that if this makes certain paths behave as shared filesystems, they should behave such without any additional tweaks > +#shared_filesystems = [ > +# "/var/lib/libvirt/images", > +# "/var/lib/libvirt/qemu/nvram", > +# "/var/lib/libvirt/swtpm" > +#] Do we want to give real paths as examples? Users might think that they are the 'suggested' values, while it really depends on how they've configured it. I sugest using something clearly dummy here. The rest looks reasonable. _______________________________________________ Devel mailing list -- devel@xxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx
