From: Peter Maydell <peter.maydell@linaro.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
Auger Eric <eric.auger@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"peter.maydell@linaro.org qemu-devel@nongnu.org"
<qemu-devel@nongnu.org>,
"Jaggi, Manish" <Manish.Jaggi@cavium.com>
Subject: Re: [Qemu-devel] [Query] Live Migration between machines with different processor ids
Date: Tue, 4 Sep 2018 13:17:51 +0100 [thread overview]
Message-ID: <CAFEAcA9Qj0KVvPgerGbMBf8PgsbWFWqQuuzmMr6k58PGDdERPg@mail.gmail.com> (raw)
In-Reply-To: <20180904103213.GB2529@work-vm>
On 4 September 2018 at 11:32, Dr. David Alan Gilbert
<dgilbert@redhat.com> wrote:
> * Andrew Jones (drjones@redhat.com) wrote:
>> Simply, users that migrate '-cpu host' VMs need to know what they're
>> doing.
>
> The problem here is that in the x86 world we've said:
> 'don't use -cpu host
> if you're using it be careful and you need to know what you're doing'
>
> on ARM it's looking like the default; that means lots more people will
> use it who don't know what they're doing.
It is also the case that on Arm migration of -cpu host means you
need to know what you're doing. But also, we don't support any
kind of cross-cpu-type migration or "present cpu type A to the guest
when running cpu type B", so a lot of the things you can do on
x86 just aren't possible (yet) on Arm. The vague plan has been that
we should fill in the gaps generally in line with what x86 does.
But as Andrew says the errata-workaround-enablement issue is a bit
tricky.
thanks
-- PMM
next prev parent reply other threads:[~2018-09-04 12:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 6:39 [Qemu-devel] Live Migration between machines with different processor ids Mjaggi Oss
2018-08-23 11:18 ` [Qemu-devel] [Query] " Jaggi, Manish
2018-08-23 14:29 ` Juan Quintela
2018-08-24 9:24 ` Jaggi, Manish
2018-08-28 17:27 ` Dr. David Alan Gilbert
2018-08-29 12:40 ` Jaggi, Manish
2018-08-29 13:16 ` Andrew Jones
2018-08-31 9:52 ` Jaggi, Manish
2018-08-31 11:11 ` Andrew Jones
2018-09-04 9:16 ` Jaggi, Manish
2018-09-04 9:54 ` Andrew Jones
2018-09-04 10:27 ` Juan Quintela
2018-09-04 10:32 ` Dr. David Alan Gilbert
2018-09-04 12:17 ` Peter Maydell [this message]
2018-09-05 11:46 ` Jaggi, Manish
2018-09-05 12:20 ` Andrew Jones
2018-09-05 12:42 ` Jaggi, Manish
2018-09-05 13:17 ` Andrew Jones
2018-08-29 13:58 ` Dr. David Alan Gilbert
2018-08-31 9:41 ` Juan Quintela
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=CAFEAcA9Qj0KVvPgerGbMBf8PgsbWFWqQuuzmMr6k58PGDdERPg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Manish.Jaggi@cavium.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=eric.auger@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 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.