From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Use host CPUID processor info
Date: Sun, 08 Jul 2007 18:12:12 +0300 [thread overview]
Message-ID: <4690FECC.5070307@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A01B8F4B3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> Avi Kivity wrote:
>
>> One of the uses of virtualization is to abstract the underlying
>> hardware, so that a VM image can run on any platform (live
>> migration is
>> an example of this use case). For that we must not let any detail of
>> the hardware be visible.
>>
>
> I doutb about the live migration cross different architecture. A VM
> using AMD 3DNow can't be migrated to Intel Box. Even within Intel
> processores, A VM using SSE2 can't be migrated to a platform w/o SSE2
> support.
>
> Only if the VM is using the minimal instruction set, minimal features
> may be able to live migrate to other platforms. If this is the purpose,
> probably we can use an ancient processor model for the VM to achieve
> best migration capability in case hybrid processor is adopted. In that
> way we meet both requirement: live migration and app doesn't know it is
> a VM.
>
It doesn't have to be too ancient. All virtualization capable
processors support at least sse2 (and maybe sse3 too).
> Further more, there needs a capibility check for live migration to see
> if it can be migrated to a new platform. If we use host processor model,
> Qemu can simply check both new processor model and required one to see
> if migration can be done, if we use virtual processor model, say qemu
> processor, we have trouble: A vm using qemu processor compiled with SSE2
> can't be migrated to a new platform w/o SSE2 though the capability check
> at migration decision make time says OK (both are qemu processoe).
No, you only need to check that the host processor is a superset of the
virtualized processor.
A management solution can also compute a cpuid that is common to all
machines in the farm and tell qemu to use that via the command line.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-07-08 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 6:47 Use host CPUID processor info Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01B8F3FB-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08 8:09 ` Avi Kivity
[not found] ` <46909BC5.1040505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-08 13:45 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01B8F4A3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08 13:49 ` Avi Kivity
[not found] ` <4690EB75.1030702-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-08 14:07 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01B8F4B3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-08 15:12 ` Avi Kivity [this message]
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=4690FECC.5070307@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.