Gerd Hoffmann wrote: > Avi Kivity wrote: > >> Agree, but should try a "quit" monitor command first. Signals are racy, >> like anything that deals with pids (qemu dies, another process is >> fork()ed with the same pid, libvirt kills it). >> > > There is no race in that specific case because qemu is started by > libvirtd. libvirtd can savely kill qemu as long as it hasn't collected > the exit status via waitpid(). While the qemu zombie hangs around the > pid will not be reused. > >
Ah good. It does mean that the we can't recover from an untimely libvirtd death, but I'd consider it a reasonable tradeoff. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
