On Tue, Oct 25, 2022 at 2:52 PM Daniel P. Berrangé <[email protected]> wrote: > If doing it in libvirt the flow would be > > libvirtd -> fork -> fork -> execve(qemu) > \-> clone(async handler) > > In the latter case the async handler would be running code from > the libvirt binary. When the parent calls execve that will load > the code from QEMU, and because of CLONE_VM, this affect the > memory mappings in the async handler process too. I think that > will end up quite explody, no ?
Oh yes it will. :) Paolo
