New code tries SIGTERM first, with a grace period of 30 seconds:

On Wed, Sep 26, 2018 at 6:10 PM Richard W.M. Jones <> wrote:
On Wed, Sep 26, 2018 at 04:57:19PM +0200, Fabien Dupont wrote:
> It's not virt-v2v-wrapper that kills virt-v2v, it's ManageIQ. We have the
> PID from virt-v2v-wrapper state file. What would be the preferred way
> to interrupt it ?

It's not too nice to send kill -9 to virt-v2v because it means none of
the at-exit handlers get to run, so it will leave temporary files all
over the place.  It's better to send an ordinary kill signal
(eg. SIGTERM).  If virt-v2v doesn't exit after some grace period,
eg. 30 seconds, then it's a bug, but maybe you could then send

This is actually another thing which a temporary systemd unit will
solve for us:


Richard Jones, Virtualization Group, Red Hat
Read my programming and virtualization blog:
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.


Fabien Dupont


Red Hat - Solutions Engineering     M: +33 (0) 662 784 971


Twitter: @redhatway | Instagram: @redhatinc | Snapchat: @redhatsnaps