From: Andre Przywara <andre.przywara@amd.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPUID feature bits not saved with migration
Date: Thu, 16 Jul 2009 12:08:22 +0200 [thread overview]
Message-ID: <4A5EFC16.7070808@amd.com> (raw)
In-Reply-To: <20090715151234.GA28724@shareable.org>
Jamie Lokier wrote:
> Anthony Liguori wrote:
>> It's unclear what to do about -cpu host. If we did migrate cpuid
>> values, then -cpu would effectively be ignored after an incoming migration.
>
> The new host might not support all the cpuid features of the old host,
> whether by -cpu host or explicit cpuid. What happens then?
If you plan to migrate, you should think of this in advance. I have a
rough version of a tool to compute the least common denominator CPUID
bits given either processor (code)names or host names. In the latter
case it will login into the box and query the host's CPUID. The tool
then generates a QEMU command line (like -cpu qemu64,-mwait,-popcnt)
with which the guest should be started.
This should ensure that the guest always sees the same subset of the
CPUs capabilities.
> For changing cpuid when migrating, as you might like to do with -cpu
> host for performance, is reboot-during-migrate useful? It would make
> sure all disk state is committed to the image files asynchronously
> while the machine continues to run (just like normal migration), and
> at the last moment transfers control and the machine sees a reboot,
> permitting devices changes including cpuid change.
Is that really useful? After all the sexy part of live migration is the
"live" component...
> CPU hotplug could be used for cpuid change in theory, but I doubt if
> any guests or guest apps would handle it well.
Hotplugging could work for secondary processors, but hotplugging the BSP
is kind of tricky. And this does not solve the userspace issues, where
libraries detect CPU capabilities during startup and use optimized code
paths. AFAIK there is no mechanism of informing those libraries about a
CPUID change.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-07-16 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 12:50 [Qemu-devel] CPUID feature bits not saved with migration Andre Przywara
2009-07-15 14:38 ` Anthony Liguori
2009-07-15 15:12 ` Jamie Lokier
2009-07-16 6:55 ` Dor Laor
2009-07-16 10:09 ` Andre Przywara
2009-07-16 14:29 ` Jamie Lokier
2009-07-16 10:08 ` Andre Przywara [this message]
2009-07-16 14:28 ` Jamie Lokier
2009-07-22 13:24 ` Andre Przywara
2009-07-22 14:46 ` Jamie Lokier
2009-07-16 10:08 ` Andre Przywara
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=4A5EFC16.7070808@amd.com \
--to=andre.przywara@amd.com \
--cc=jamie@shareable.org \
--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 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).