On 25.10.2013 07:42, Eric Blake wrote:
On 10/25/2013 04:27 AM, Peter Lieven wrote:
Ok, one way direction - i forgot about this paradigm.
2 thoughts:
a) a send-capabilities capability that "stores" the capabilities that where
used when savevm was used. I would implement a special segment
right
On 10/25/2013 04:27 AM, Peter Lieven wrote:
> Ok, one way direction - i forgot about this paradigm.
>
> 2 thoughts:
>
> a) a send-capabilities capability that "stores" the capabilities that where
> used when savevm was used. I would implement a special segment
> right at the beginning of the dat
Am 25.10.2013 um 01:37 schrieb Juan Quintela :
> Peter Lieven wrote:
>> Hi,
>>
>> I was thinking that it would be great to have the source and
>> destination during migration negoatiate
>> migration capabilities e.g. something like this:
>>
>> User wants to use a feature e.g. 'zero_blocks'. He
Peter Lieven wrote:
> Hi,
>
> I was thinking that it would be great to have the source and
> destination during migration negoatiate
> migration capabilities e.g. something like this:
>
> User wants to use a feature e.g. 'zero_blocks'. He switches it to 'on'
> or maybe a new state 'auto' on the so
On 10/24/2013 07:39 PM, Peter Lieven wrote:
> Hi,
>
> I was thinking that it would be great to have the source and destination
> during migration negoatiate
> migration capabilities e.g. something like this:
>
> User wants to use a feature e.g. 'zero_blocks'. He switches it to 'on' or
> maybe a
Hi,
I was thinking that it would be great to have the source and destination during
migration negoatiate
migration capabilities e.g. something like this:
User wants to use a feature e.g. 'zero_blocks'. He switches it to 'on' or maybe
a new state 'auto' on the source VM.
If the migration is sta
