On Tue, Jun 02, 2015 at 17:37:35 +0200, Ján Tomko wrote:
On Mon, Jun 01, 2015 at 09:05:59PM +0200, Jiri Denemark wrote:
When watching a job (save, managedsave, dump, migrate) virsh spawns a
thread to call the appropriate API and waits for the result while
watching for interruption signals
On Mon, Jun 01, 2015 at 09:05:59PM +0200, Jiri Denemark wrote:
When watching a job (save, managedsave, dump, migrate) virsh spawns a
thread to call the appropriate API and waits for the result while
watching for interruption signals (SIGINT, Ctrl-C on the terminal).
Whenever such signal is
When watching a job (save, managedsave, dump, migrate) virsh spawns a
thread to call the appropriate API and waits for the result while
watching for interruption signals (SIGINT, Ctrl-C on the terminal).
Whenever such signal is caught, virsh calls virDomainAbortJob, stops
waiting for the job, and
