Re: [PATCH] qemu_namespace: Umount the original /dev before replacing it with tmpfs

2023-01-17 Thread Michal Prívozník
On 1/18/23 01:58, Jim Fehlig wrote: > On 12/16/22 08:04, Michal Privoznik wrote: >> Our code relies on mount events propagating into the namespace we >> create for a domain. However, there's one caveat. In v8.8.0-rc1~8 >> I've tried to make us detect differences in mount tables between >> the

Re: [PATCH] qemu_namespace: Umount the original /dev before replacing it with tmpfs

2023-01-17 Thread Jim Fehlig
On 12/16/22 08:04, Michal Privoznik wrote: Our code relies on mount events propagating into the namespace we create for a domain. However, there's one caveat. In v8.8.0-rc1~8 I've tried to make us detect differences in mount tables between the namespace in which libvirtd runs and the domain

Re: [PATCH] qemu_namespace: Umount the original /dev before replacing it with tmpfs

2023-01-05 Thread Martin Kletzander
On Fri, Dec 16, 2022 at 04:04:01PM +0100, Michal Privoznik wrote: Our code relies on mount events propagating into the namespace we create for a domain. However, there's one caveat. In v8.8.0-rc1~8 I've tried to make us detect differences in mount tables between the namespace in which libvirtd

[PATCH] qemu_namespace: Umount the original /dev before replacing it with tmpfs

2022-12-16 Thread Michal Privoznik
Our code relies on mount events propagating into the namespace we create for a domain. However, there's one caveat. In v8.8.0-rc1~8 I've tried to make us detect differences in mount tables between the namespace in which libvirtd runs and the domain namespace. This is crucial for any mounts that