qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Ryan Harper <ryan.harper@canonical.com>,
	Serge Hallyn <serge.hallyn@canonical.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Libvirt <libvir-list@redhat.com>,
	Serge Hallyn <serge.hallyn@ubuntu.com>,
	qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
	"quintela@redhat.com" <quintela@redhat.com>,
	Alex Bligh <alex@alex.org.uk>,
	Cole Robinson <crobinso@redhat.com>,
	Amit Shah <amit.shah@redhat.com>, Bruce Rogers <brogers@suse.com>,
	Andreas F?rber <afaerber@suse.de>,
	"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Qemu-devel] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm
Date: Thu, 25 Sep 2014 09:02:22 +0100	[thread overview]
Message-ID: <20140925080221.GA2348@work-vm> (raw)
In-Reply-To: <5422830D.20406@msgid.tls.msk.ru>

* Michael Tokarev (mjt@tls.msk.ru) wrote:
> 22.09.2014 23:34, Alex Bligh wrote:
> > This patch series adds inbound migrate capability from qemu-kvm version
> > 1.0. [...]
> 
> Isn't it quite a bit too late already?  That's an old version by
> now, and supporting migration from it is interesting for long-term
> support distributions - like redhat for example, with several
> years of release cycle.  Is it really necessary at this time to
> add this ability to upstream qemu?
> 
> It'd be very nice to have this capability right when qemu-kvm
> tree has been merged (or even before that), but it's been some
> years ago already.

It's amazing what different combinations of QEMU people have
out there; and it seems reasonable to let Alex fix this problem
if it helps him; there's no reason to deny others the same fix.

Dave

--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2014-09-25  8:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 19:34 [Qemu-devel] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm Alex Bligh
2014-09-22 19:34 ` Alex Bligh
2014-09-28 15:30   ` Michael S. Tsirkin
2014-09-28 20:33     ` Alex Bligh
2014-09-29  7:02       ` Markus Armbruster
2014-10-05  7:00         ` Paolo Bonzini
2014-10-05 10:26           ` Alex Bligh
2014-10-05 12:26             ` Paolo Bonzini
2014-10-05 12:48               ` Michael S. Tsirkin
2014-10-05 13:30                 ` Paolo Bonzini
2014-09-29 10:08       ` Michael S. Tsirkin
2014-09-29 10:13         ` Alex Bligh
2014-09-29 14:52           ` Serge E. Hallyn
2014-10-04 16:29     ` Alex Bligh
2014-09-24  8:05 ` Markus Armbruster
2014-09-24  8:29   ` Alex Bligh
2014-09-24  8:38 ` Michael Tokarev
2014-09-25  8:02   ` Dr. David Alan Gilbert [this message]

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=20140925080221.GA2348@work-vm \
    --to=dgilbert@redhat.com \
    --cc=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=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=ryan.harper@canonical.com \
    --cc=serge.hallyn@canonical.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=serge@hallyn.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).