All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] qemu live migration error from 2.0 to 2.1
Date: Wed, 6 Aug 2014 10:17:50 +0100	[thread overview]
Message-ID: <20140806091749.GB2368@work-vm> (raw)
In-Reply-To: <CAJ75kXYe4XOZ7FW=dooqPPkfBs0NH06RTM26q625CeoJLPmRog@mail.gmail.com>

* William Dauchy (wdauchy@gmail.com) wrote:
> On Wed, Aug 6, 2014 at 9:47 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > I suspect he's using "-M pc" on both.
> 
> Is it the default value? because it's not the case in my command line.
> 
> > You must use "-M pc-i440fx-2.0"
> > on both if you're migrating from 2.0 to a different version.
> 
> wow. I wasn't expecting such behavior; i.e migration between qemu
> version does not seem trivial and it removes the benefits; better
> using stop/start.
> thanks for the info.

The trick is to pick a -M value and stick with it; then you should be
able to keep migrating to newer QEMU versions easily (just don't
go with dev versions because things are often broken in them).

-M pc   is special, don't use that if you want to be able to migrate

Dave

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

  reply	other threads:[~2014-08-06  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 17:36 [Qemu-devel] qemu live migration error from 2.0 to 2.1 William Dauchy
2014-08-05 18:57 ` Dr. David Alan Gilbert
2014-08-05 19:39   ` William Dauchy
2014-08-06  6:16     ` Markus Armbruster
2014-08-06  7:49       ` Paolo Bonzini
2014-08-06  9:09         ` William Dauchy
2014-08-06  7:47   ` Paolo Bonzini
2014-08-06  9:06     ` William Dauchy
2014-08-06  9:17       ` Dr. David Alan Gilbert [this message]
2014-08-06  9:27         ` William Dauchy

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=20140806091749.GB2368@work-vm \
    --to=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdauchy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.