qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] target-ppc: enable migration within the same CPU family
Date: Mon, 07 Apr 2014 20:53:58 +0200	[thread overview]
Message-ID: <5342F446.6040303@suse.de> (raw)
In-Reply-To: <53421B2E.2060301@ozlabs.ru>

Am 07.04.2014 05:27, schrieb Alexey Kardashevskiy:
> On 04/04/2014 11:28 PM, Alexander Graf wrote:
>> On 04/04/2014 07:17 AM, Alexey Kardashevskiy wrote:
>>> On 03/24/2014 04:28 PM, Alexey Kardashevskiy wrote:
>>>> Currently only migration fails if CPU version is different even a bit.
>>>> For example, migration from POWER7 v2.0 to POWER7 v2.1 fails because of
>>>> that. Since there is no difference between CPU versions which could
>>>> affect migration stream, we can safely enable it.
>>>>
>>>> This adds a helper to find the closest POWERPC family class (i.e. first
>>>> abstract class in hierarchy).
>>>>
>>>> This replaces VMSTATE_UINTTL_EQUAL statement with a custom handler which
>>>> checks if the source and destination CPUs belong to the same family and
>>>> fails if they are not.
>>>>
>>>> This adds a PVR reset to the default value as it will be overwritten
>>>> by VMSTATE_UINTTL_ARRAY(env.spr, PowerPCCPU, 1024).
>>>>
>>>> Since the actual migration format is not changed by this patch,
>>>> @version_id of vmstate_ppc_cpu does not have to be changed either.
>>>>
>>>> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
>>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>>
>>> Ping?
>>
>> Can't we just always allow migration to succeed? It's a problem of the tool
>> stack above if it allows migration to an incompatible host, no?
> 
> This is not how libvirt works. It simply sends the source XML, reconstructs
> a guest on the destination side and then migrates. hoping that the
> migration will fail is something (which only QEMU has knowledge of) is
> incompatible. The new guest will start with "-cpu host" (as the source) but
> it will create diffrent CPU class and do different things. If we do not
> check PVR (and cpu_dt_id and chip_id - the latter is coming soon) and
> migrate power8->power7, we can easily get a broken guest.

The response is very simple: -cpu host is not supported for migration.
Same as for x86 hosts.

As you say, the domain config is transferred by libvirt:
If you use -cpu POWER7, you can migrate from POWER7 to POWER8 and back;
if you use -cpu POWER8, you can only migrate on POWER8.

Andreas

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

  reply	other threads:[~2014-04-07 18:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  5:28 [Qemu-devel] [RFC PATCH] target-ppc: enable migration within the same CPU family Alexey Kardashevskiy
2014-04-04  5:17 ` Alexey Kardashevskiy
2014-04-04 12:28   ` Alexander Graf
2014-04-07  3:27     ` Alexey Kardashevskiy
2014-04-07 18:53       ` Andreas Färber [this message]
2014-04-08  1:23         ` Alexey Kardashevskiy
2014-04-08  9:47           ` Michael Mueller
2014-04-08 10:04             ` Alexey Kardashevskiy
2014-04-08 10:32               ` Michael Mueller
2014-04-08 11:47                 ` Alexey Kardashevskiy
2014-04-08 12:19                   ` Michael Mueller
2014-04-08 14:59                     ` Alexander Graf
2014-04-09  0:41                       ` Alexey Kardashevskiy
2014-04-09  8:02                         ` Alexander Graf
2014-04-10 16:03                 ` Alexey Kardashevskiy
2014-04-10 17:41                   ` Michael Mueller
2014-04-10 15:11     ` Alexey Kardashevskiy
2014-04-10 15:42       ` Michael Mueller

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=5342F446.6040303@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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).