Re: [libvirt] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm

2014-10-05 Thread Paolo Bonzini
Il 05/10/2014 14:48, Michael S. Tsirkin ha scritto: > In fact, if the pc_piix bits are dropped from the patch, > you get a generic patchset that does exactly what you ask, > correct? > > Downstream can then enable qemu-kvm compatibility by adding: > > -global cirrus-vga.vgamem_mb=16 -global pit-c

Re: [libvirt] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm

2014-10-05 Thread Paolo Bonzini
Il 29/09/2014 09:02, Markus Armbruster ha scritto: >> If you were just objecting to the fact that pc-1.0 was made to >> be an alias of either one or the other at compile time, simply >> drop the second patch of the v2 patchset. I was objecting to making pc-1.0 special. There's nothing special in

Re: [libvirt] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm

2014-09-28 Thread Michael S. Tsirkin
On Mon, Sep 22, 2014 at 08:34:56PM +0100, Alex Bligh wrote: > Add a machine parameter qemu-kvm-migration for live migrate compatibility > with qemu-kvm version 1.0. Usage: > -machine pc-1.0,qemu-kvm-migration=on I would rename "migration" to "compatibility" everywhere. Though it's a matter of

[libvirt] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm

2014-09-22 Thread Alex Bligh
This patch series adds inbound migrate capability from qemu-kvm version 1.0. The main ideas are those set out in Cole Robinson's patch here: http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20 however, rather than patching statically (and breaking inbound m

[libvirt] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm

2014-09-22 Thread Alex Bligh
Add a machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm version 1.0. Usage: -machine pc-1.0,qemu-kvm-migration=on This has three effects: 1. cirrus-vga.vgamem_mb defaults to 16 rather than 8 2. A type 2 piix4_pm record is interpreted as being type 3 3. A type 2