All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: "Anshul Makkar" <anshul.makkar@profitbricks.com>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration + licensing issue.
Date: Fri, 11 Jul 2014 14:19:33 +0200	[thread overview]
Message-ID: <87sim83x62.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <CAEVwAuMXfXYER=ekJ6BEiPEmWmSeZ+Erbe_JEmU442gtU290DQ@mail.gmail.com> (Eduardo Otubo's message of "Fri, 11 Jul 2014 13:52:34 +0200")

Eduardo Otubo <eduardo.otubo@profitbricks.com> writes:

> On Fri, Jul 11, 2014 at 1:12 PM, Markus Armbruster <armbru@redhat.com> wrote:
>> [Top-quote moved to its rightful place; please do not top quote on
>> technical lists]
>>
>> Anshul Makkar <anshul.makkar@profitbricks.com> writes:
>>
>>> On Wed, Jul 9, 2014 at 6:25 PM, Andreas Färber <afaerber@suse.de> wrote:
>>>> Am 09.07.2014 13:09, schrieb Anshul Makkar:
>>>>> Thanks. I got the point.
>>>>
>>>> And for the record, the point is that the machine version on the
>>>> destination side needs to match the source side. So, if the default or
>>>> "pc" alias is used in 1.0, which resolves to pc-1.0, then it needs to be
>>>> pc-1.0, not pc-1.2. If an explicit machine name such as pc-0.15 was used
>>>> then that exact machine must be used on the destination as well.
>>
>>> Hi Andreas,
>>>
>>> "the point is that the machine version on the destination side needs
>>> to match the source side". I hope this is just to avoid the licensing
>>> issue. Else, in all other circumstance, we can specify different pc
>>> models while migrating from source to destination.
>>
>> You certainly can specify whatever machine type you want, but if you
>> specify different machine types on source and target of a migration, all
>> bets are off.
>>
>> It could succeed if the stars align the right way.  It could break
>> obviously and immediately, leaving your machine running on the source.
>> It could migrate your machine to the destination successfully, then blow
>> up there right away, or some time later, taking down your machine.  It
>> could migrate successfully, but silently corrupt data.
>>
>> Regardless of how it breaks, you get to keep the pieces.
>
> What you're saying is that there's no way to migrate (live or offline)
> from Qemu 1.0/1.2 to 2.0 in a *safe way* whatever OS I'm running on
> it?

No, what I'm saying is you need to use the same machine type on source
on destination.

If you don't specify one, you get the default.  If you run different
versions of QEMU on source and destination, their default machine type
may differ.

In that case, find the default machine type on the source (-M help shows
it), then start QEMU on the destination with that machine type.

  reply	other threads:[~2014-07-11 12:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 15:24 [Qemu-devel] live migration + licensing issue Anshul Makkar
2014-07-08 16:25 ` Andreas Färber
2014-07-08 21:10   ` Anshul Makkar
2014-07-09  7:36     ` Markus Armbruster
2014-07-09 11:09       ` Anshul Makkar
2014-07-09 16:17         ` Alexandre DERUMIER
2014-07-09 16:25         ` Andreas Färber
2014-07-11 10:14           ` Anshul Makkar
2014-07-11 11:09             ` Paolo Bonzini
2014-07-11 11:12             ` Markus Armbruster
2014-07-11 11:50               ` Anshul Makkar
2014-07-11 12:20                 ` Markus Armbruster
2014-07-11 11:52               ` Eduardo Otubo
2014-07-11 12:19                 ` Markus Armbruster [this message]
2014-07-11 12:29                   ` Eduardo Otubo
2014-07-11 12:41                     ` Markus Armbruster
2014-07-10 23:19     ` Eric Blake
2014-07-11 10:12       ` Anshul Makkar

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=87sim83x62.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anshul.makkar@profitbricks.com \
    --cc=eduardo.otubo@profitbricks.com \
    --cc=qemu-devel@nongnu.org \
    /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.