Re: [Libguestfs] external call to v2v (vdsm integration)

On Mon, Sep 15, 2014 at 02:16:32PM +0300, Shahar Havivi wrote: The program will either exit with status 0 (success) or non-zero (failure). It will print an error messsage to stderr before it exits. Note that 'virt-v2v -o vdsm' mode assumes that VDSM is going to create Data Storage Domain directories before it runs, and clean them up on failure! I hope this was clear when RHBZ#1140156 was done. One way to deal with this is to have a small wrapper that handles virt-v2v, and receives commands from vdsm over a socket. If you assume that the wrapper is small, mostly bug free and so cannot crash, then VDSM can reconnect to the wrapper in the event that it crashes or is restarted. Socket commands would be similar to: "Is virt-v2v running?" "Send me the latest output" "Send me the exit code" etc. A simpler way is to send a signal (eg. SIGTERM) to virt-v2v when vdsm goes down (assuming that you have somewhere that handles vdsm crashes). Virt-v2v should stop the conversion and exit fairly quickly after receiving a signal (maybe not instantly). If it doesn't then that's a virt-v2v bug. If you just run virt-v2v with neither of these options, then there is the chance that virt-v2v will still be running -- unknown to you -- when VDSM starts up again. This is probably not what you want. Not sure what this question means. Can you give an example of how a blocked I/O call would affect things? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v