qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Alex Bligh <alex@alex.org.uk>, qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
	Libvirt <libvir-list@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Alexander Graf <agraf@suse.de>, Bruce Rogers <brogers@suse.com>,
	Cole Robinson <crobinso@redhat.com>,
	Amit Shah <amit.shah@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm
Date: Sun, 27 Jul 2014 16:10:51 +0200	[thread overview]
Message-ID: <53D5086B.9070008@suse.de> (raw)
In-Reply-To: <1406054580-16763-1-git-send-email-alex@alex.org.uk>

Hi Alex,

+ quintela, mst, libvirt

Am 22.07.2014 20:43, schrieb Alex Bligh:
> Add a machine type pc-1.0-qemu-kvm for live migrate compatibility
> with qemu-kvm version 1.0.
> 
> Signed-off-by: Alex Bligh <alex@alex.org.uk>
> ---
>  hw/acpi/piix4.c          |   49 ++++++++++++++++++++++++++++++++++++++++++++--
>  hw/i386/pc_piix.c        |   31 +++++++++++++++++++++++++++++
>  hw/timer/i8254_common.c  |   41 ++++++++++++++++++++++++++++++++++++++
>  include/hw/acpi/piix4.h  |    1 +
>  include/hw/timer/i8254.h |    2 ++
>  5 files changed, 122 insertions(+), 2 deletions(-)
> 
> This RFC patch 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
> migration on existing machine types), I have added a new machine
> type (pc-1.0-qemu-kvm) without affecting any other machine types.

This sounds like a really cool feature that SUSE would probably be
interested in extending back to 0.14 and 0.15, but I see a fundamental
flaw: libvirt on those old source systems does not know it should use a
different machine name on the destination side and would still use
pc-1.0, wouldn't it? After all, it needs to be able to migrate to other
old qemu-kvm machines, so it can't just be updated to use the new name.

Minor bikeshedding: I would ask to keep the package name in front of the
machine version, e.g. qemu-kvm-pc-1.0. Or just kvm-pc-1.0 since this is
a QEMU parameter anyway.

Haven't reviewed the code in detail yet.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2014-07-27 14:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 18:43 [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm Alex Bligh
2014-07-25 16:01 ` Alex Bligh
2014-07-26  7:38   ` Paolo Bonzini
2014-07-27 13:09 ` Alex Bligh
2014-07-27 14:10 ` Andreas Färber [this message]
2014-07-27 17:04   ` Alex Bligh
2014-07-27 21:03 ` Alex Bligh
2014-07-29  4:16   ` Serge Hallyn
2014-07-29  7:31     ` Alex Bligh
2014-07-29 13:03       ` Serge E. Hallyn
2014-07-29 13:15         ` Alex Bligh
2014-07-29 13:21         ` Paolo Bonzini
2014-07-29 13:27           ` Serge Hallyn
2014-07-29 13:35             ` Paolo Bonzini
2014-07-29 13:39               ` Alex Bligh
2014-07-29 13:42                 ` Paolo Bonzini
2014-07-29 13:56                   ` Alex Bligh
2014-07-29 14:00                     ` Paolo Bonzini
2014-07-29 15:05                       ` Alex Bligh
2014-07-29 13:41               ` Serge Hallyn
2014-07-29 13:38           ` Alex Bligh
2014-07-29 13:41             ` Serge Hallyn
2014-08-04 13:34       ` Michael S. Tsirkin
2014-08-04 15:08         ` Serge Hallyn
2014-08-04 15:26           ` Michael S. Tsirkin
2014-08-04 15:38             ` Serge Hallyn
2014-08-04 15:47               ` Alex Bligh
2014-08-04 16:13                 ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53D5086B.9070008@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=alex@alex.org.uk \
    --cc=amit.shah@redhat.com \
    --cc=brogers@suse.com \
    --cc=crobinso@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).