Re: [libvirt] [PATCH] create a thread to handle MigrationParamReset to avoid deadlock

2019-12-23 Thread Daniel P . Berrangé
On Mon, Dec 23, 2019 at 04:50:00PM +0100, Michal Prívozník wrote: > On 12/23/19 11:12 AM, Daniel P. Berrangé wrote: > > On Mon, Dec 23, 2019 at 03:13:10PM +0800, Yi Wang wrote: > >> From: Li XueLei > >> > >> Libvirtd no longer receives external requests, after I do the following. > >> > >> Steps

Re: [libvirt] [PATCH] create a thread to handle MigrationParamReset to avoid deadlock

2019-12-23 Thread Michal Prívozník
On 12/23/19 11:12 AM, Daniel P. Berrangé wrote: > On Mon, Dec 23, 2019 at 03:13:10PM +0800, Yi Wang wrote: >> From: Li XueLei >> >> Libvirtd no longer receives external requests, after I do the following. >> >> Steps to reproduce: >> 1.Virsh tool initiates a non-p2p migrations. >> 2.After the

Re: [libvirt] [PATCH] create a thread to handle MigrationParamReset to avoid deadlock

2019-12-23 Thread Daniel P . Berrangé
On Mon, Dec 23, 2019 at 03:13:10PM +0800, Yi Wang wrote: > From: Li XueLei > > Libvirtd no longer receives external requests, after I do the following. > > Steps to reproduce: > 1.Virsh tool initiates a non-p2p migrations. > 2.After the phase of qemuDomainMigratePerform3 and before the phase of

[libvirt] [PATCH] create a thread to handle MigrationParamReset to avoid deadlock

2019-12-23 Thread Yi Wang
From: Li XueLei Libvirtd no longer receives external requests, after I do the following. Steps to reproduce: 1.Virsh tool initiates a non-p2p migrations. 2.After the phase of qemuDomainMigratePerform3 and before the phase of qemuDomainMigrateConfirm3, kill the virsh client which initiated the