On 20/11/2014 08:55, Michael S. Tsirkin wrote:
On Thu, Nov 20, 2014 at 08:11:05AM +0100, Paolo Bonzini wrote:
On 20/11/2014 07:55, Michael S. Tsirkin wrote:
I thought we agreed we'll consider alternate approaches after 2.2?
I would prefer not to have yet another mode to support
if we can
On Thu, Nov 20, 2014 at 11:04:13AM +0100, Paolo Bonzini wrote:
On 20/11/2014 08:55, Michael S. Tsirkin wrote:
On Thu, Nov 20, 2014 at 08:11:05AM +0100, Paolo Bonzini wrote:
On 20/11/2014 07:55, Michael S. Tsirkin wrote:
I thought we agreed we'll consider alternate approaches after
On 11/11/2014 18:13, Paolo Bonzini wrote:
On 06/10/2014 16:56, Paolo Bonzini wrote:
In the emergency last-minute patches of QEMU 2.1 we did two things:
- fixed migration problems from 1.7 or 2.0 to 2.1 due to changes in
ACPI table sizes
- ensured that future versions will not break
On Thu, Nov 20, 2014 at 07:05:05AM +0100, Paolo Bonzini wrote:
On 11/11/2014 18:13, Paolo Bonzini wrote:
On 06/10/2014 16:56, Paolo Bonzini wrote:
In the emergency last-minute patches of QEMU 2.1 we did two things:
- fixed migration problems from 1.7 or 2.0 to 2.1 due to changes
On 20/11/2014 07:55, Michael S. Tsirkin wrote:
I thought we agreed we'll consider alternate approaches after 2.2?
I would prefer not to have yet another mode to support
if we can help it.
I agree, but:
1) looks like there is stronger opposition to your patch than I thought,
so a 2.2
On Thu, Nov 20, 2014 at 08:11:05AM +0100, Paolo Bonzini wrote:
On 20/11/2014 07:55, Michael S. Tsirkin wrote:
I thought we agreed we'll consider alternate approaches after 2.2?
I would prefer not to have yet another mode to support
if we can help it.
I agree, but:
1) looks like
On 06/10/2014 16:56, Paolo Bonzini wrote:
In the emergency last-minute patches of QEMU 2.1 we did two things:
- fixed migration problems from 1.7 or 2.0 to 2.1 due to changes in
ACPI table sizes
- ensured that future versions will not break migration compatibility
with 2.2 for
In the emergency last-minute patches of QEMU 2.1 we did two things:
- fixed migration problems from 1.7 or 2.0 to 2.1 due to changes in
ACPI table sizes
- ensured that future versions will not break migration compatibility
with 2.2 for reasonable configurations (with ACPI tables smaller
