On Oct 8, 2013, at 12:05 PM, Paolo Bonzini wrote:
> Il 08/10/2013 16:49, Eric Blake ha scritto:
>> You are now returning a state that older libvirt versions are not
>> expecting. Obviously, we can patch newer libvirt to make migration work
>> again, but should we be thinking about damage con
On 10/08/2013 11:32 AM, Michael R. Hines wrote:
>>
>> In this case, in particular, I think a capability is a bit overkill.
>> Libvirt needs to be somewhat liberal in what it accepts; in this case it
>> can treat any unknown state as "active".
>>
>> Paolo
>
> That makes sense to me too - the setup
On 10/08/2013 12:05 PM, Paolo Bonzini wrote:
Il 08/10/2013 16:49, Eric Blake ha scritto:
You are now returning a state that older libvirt versions are not
expecting. Obviously, we can patch newer libvirt to make migration work
again, but should we be thinking about damage control by stating tha
Il 08/10/2013 16:49, Eric Blake ha scritto:
> You are now returning a state that older libvirt versions are not
> expecting. Obviously, we can patch newer libvirt to make migration work
> again, but should we be thinking about damage control by stating that an
> older management app should still b
On 07/22/2013 08:01 AM, mrhi...@linux.vnet.ibm.com wrote:
> From: "Michael R. Hines"
>
> As described in the previous patch, until now, the MIG_STATE_SETUP
> state was not really a 'formal' state. It has been used as a 'zero' state
> (what we're calling 'NONE' here) and QEMU has been unconditiona
From: "Michael R. Hines"
As described in the previous patch, until now, the MIG_STATE_SETUP
state was not really a 'formal' state. It has been used as a 'zero' state
(what we're calling 'NONE' here) and QEMU has been unconditionally transitioning
into this state when the QMP migration command was
From: "Michael R. Hines"
As described in the previous patch, until now, the MIG_STATE_SETUP
state was not really a 'formal' state. It has been used as a 'zero' state
(what we're calling 'NONE' here) and QEMU has been unconditionally transitioning
into this state when the QMP migration command was
