Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-21 Thread Christian Borntraeger
On 09/20/2017 06:04 PM, Dr. David Alan Gilbert wrote: > * Christian Borntraeger (borntrae...@de.ibm.com) wrote: >> Something like the following seems to do the tricks. >> Needs proper patch description, review, full test with different kernel >> versions. > > Without knowing anything about

Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-20 Thread Yi Min Zhao
在 2017/9/21 上午12:04, Dr. David Alan Gilbert 写道: * Christian Borntraeger (borntrae...@de.ibm.com) wrote: Something like the following seems to do the tricks. Needs proper patch description, review, full test with different kernel versions. Without knowing anything about 'ais' - will this

Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-20 Thread no-reply
Hi, This series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] block ais migration for machines <= 2.9 Message-id: f6da1ec7-4845-fe78-b6b8-29a71d481...@de.ibm.com Type: series === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1

Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-20 Thread Dr. David Alan Gilbert
* Christian Borntraeger (borntrae...@de.ibm.com) wrote: > Something like the following seems to do the tricks. > Needs proper patch description, review, full test with different kernel > versions. Without knowing anything about 'ais' - will this break migration from 2.10 -> 2.10+this fix?

Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-20 Thread Christian Borntraeger
On 09/20/2017 02:59 PM, Cornelia Huck wrote: > On Wed, 20 Sep 2017 14:53:07 +0200 > Christian Borntraeger wrote: > >> Something like the following seems to do the tricks. >> Needs proper patch description, review, full test with different kernel >> versions. > >

Re: [Qemu-devel] block ais migration for machines <= 2.9

2017-09-20 Thread Cornelia Huck
On Wed, 20 Sep 2017 14:53:07 +0200 Christian Borntraeger wrote: > Something like the following seems to do the tricks. > Needs proper patch description, review, full test with different kernel > versions. Looks sane. Will you handle it? > > diff --git