Re: [libvirt] [PATCH] Don't start a nested job in qemuMigrationPrepareAny

2013-11-22 Thread Jiri Denemark
On Tue, Nov 19, 2013 at 18:21:08 +0100, Jano Tomko wrote: This nested job is canceled by the first ExitMonitor call (even though it was not created by the corresponding EnterMonitor call), and again in qemuMigrationPrepareAny if qemuProcessStart failed. This can lead to a crash if the vm

Re: [libvirt] [PATCH] Don't start a nested job in qemuMigrationPrepareAny

2013-11-22 Thread Ján Tomko
On 11/22/2013 04:21 PM, Jiri Denemark wrote: On Tue, Nov 19, 2013 at 18:21:08 +0100, Jano Tomko wrote: This nested job is canceled by the first ExitMonitor call (even though it was not created by the corresponding EnterMonitor call), and again in qemuMigrationPrepareAny if qemuProcessStart

[libvirt] [PATCH] Don't start a nested job in qemuMigrationPrepareAny

2013-11-19 Thread Ján Tomko
This nested job is canceled by the first ExitMonitor call (even though it was not created by the corresponding EnterMonitor call), and again in qemuMigrationPrepareAny if qemuProcessStart failed. This can lead to a crash if the vm object was disposed of before calling qemuDomainRemoveInactive: 0