On 11/23/2011 09:34 AM, Juan Quintela wrote:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migration (qemu -incoming tcp:...)
- start qemu on source of migration an
Am 09.11.2011 22:16, schrieb Anthony Liguori:
> On 11/09/2011 03:10 PM, Juan Quintela wrote:
>> Anthony Liguori wrote:
>>> On 11/09/2011 01:16 PM, Juan Quintela wrote:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
>>>
On 11/09/2011 05:16 PM, Juan Quintela wrote:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migration (qemu -incoming tcp:...)
- start qemu on source of migration an
On 11/09/2011 03:10 PM, Juan Quintela wrote:
Anthony Liguori wrote:
On 11/09/2011 01:16 PM, Juan Quintela wrote:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migrati
Anthony Liguori wrote:
> On 11/09/2011 01:16 PM, Juan Quintela wrote:
>> We need to invalidate the Read Cache on the destination, otherwise we
>> have corruption. Easy way to reproduce it is:
>>
>> - create an qcow2 images
>> - start qemu on destination of migration (qemu -incoming tcp:...)
On 11/09/2011 01:16 PM, Juan Quintela wrote:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migration (qemu -incoming tcp:...)
- start qemu on source of migration an
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migration (qemu -incoming tcp:...)
- start qemu on source of migration and do one install.
- migrate at the end of insta