Re: [PATCH 0/3] Add a retry procedure after failing to do post parsing

2022-05-09 Thread Daniel P . Berrangé
On Mon, May 09, 2022 at 10:22:56AM +0200, Peter Krempa wrote: > On Mon, May 09, 2022 at 09:12:51 +0100, Daniel P. Berrangé wrote: > > On Sat, May 07, 2022 at 05:40:13PM +0800, zhangjl02 wrote: > > > Get default emulator based on guest's arch, and replace it in domain's > > > definition after domain

Re: [PATCH 0/3] Add a retry procedure after failing to do post parsing

2022-05-09 Thread Peter Krempa
On Mon, May 09, 2022 at 09:12:51 +0100, Daniel P. Berrangé wrote: > On Sat, May 07, 2022 at 05:40:13PM +0800, zhangjl02 wrote: > > Get default emulator based on guest's arch, and replace it in domain's > > definition after domainPostParseDataAlloc's failure, then alloc again. > > This will solve th

Re: [PATCH 0/3] Add a retry procedure after failing to do post parsing

2022-05-09 Thread Daniel P . Berrangé
On Sat, May 07, 2022 at 05:40:13PM +0800, zhangjl02 wrote: > Get default emulator based on guest's arch, and replace it in domain's > definition after domainPostParseDataAlloc's failure, then alloc again. > This will solve the migration problem because of qemu emulator location error, > especially,

[PATCH 0/3] Add a retry procedure after failing to do post parsing

2022-05-07 Thread zhangjl02
Get default emulator based on guest's arch, and replace it in domain's definition after domainPostParseDataAlloc's failure, then alloc again. This will solve the migration problem because of qemu emulator location error, especially, from host with to host without qemu-kvm. This commit will also all