On Tue, Aug 21, 2018 at 02:33:25PM +0200, Christian Ehrhardt wrote: > It was found that in cases with host devices virProcessKillPainfully > might be able to send signal zero to the target PID for quite a while > with the process already being gone from /proc/<PID>. > > That is due to cleanup and reset of devices which might include a > secondary bus reset that on top of the actions taken has a 1s delay > to let the bus settle. Due to that guests with plenty of Host devices > could easily exceed the default timeouts. > > To solve that, this adds an extra delay of 2s per hostdev that is associated > to a VM. > > Signed-off-by: Christian Ehrhardt <christian.ehrhardt@xxxxxxxxxxxxx> > --- > src/libvirt_private.syms | 1 + > src/qemu/qemu_process.c | 7 +++++-- > src/util/virprocess.c | 20 +++++++++++++++++--- > src/util/virprocess.h | 3 +++ > 4 files changed, 26 insertions(+), 5 deletions(-) Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
