All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: John Byrne <john.l.byrne@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Migration and CPU type?
Date: Thu, 16 Feb 2006 12:25:07 -0600	[thread overview]
Message-ID: <43F4C383.5040303@us.ibm.com> (raw)
In-Reply-To: <43F3BE60.1040901@hp.com>

John Byrne wrote:
>
> There are various differences between x86 CPU types that I believe 
> would cause a guest to fail after being migrated. Are there checks in 
> the migration code to prevent this from happening? Does it check for 
> an "incompatible CPU" and fail early, leaving the guest running on the 
> source host? If there is a check, what is its nature? (Exact match of 
> CPU type/rev or something based on CPU-features?)
This, unfortunately, is always going to be a heuristic.  There's no way 
to guarantee CPU compatibility (except, of course, with VT/SVM).  The 
major problem is the CPUID instruction.  If an application obtains CPUID 
info (which I think can even contain a serial number for the processor), 
and relies on this info (even for something simple like CPU frequency), 
it will break when moved to another CPU that doesn't have the same exact 
information reported for CPUID.

This is a bit contrived but important as a base case to assert that 
there's no completely safe heuristic for migration.

There are going to, of course, be common cases of incompatibility mostly 
related to things like the presence of SIMD instructions.  One can argue 
that for a lot server work loads, this isn't going to be an issue.  I 
don't think it's horrible that Xend doesn't do any checking right now 
because of this.  It certainly wouldn't be harmful to do some checking 
and issue a warning to the user before migration.

Personally, I think it's far easier for high level tools to take care of 
this since they will have a better idea of the cluster's hardware layout 
and can make appropriate decisions based on risk compared to availability.

Regards,

Anthony Liguori
> Thanks,
>
> John Byrne
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2006-02-16 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 23:50 Migration and CPU type? John Byrne
2006-02-16 18:25 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-16  8:53 Noam Taich
2006-02-16 16:56 ` John Byrne
2006-02-16 17:18   ` Ralph Passgang
2006-02-16 18:32 ` Anthony Liguori

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=43F4C383.5040303@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=john.l.byrne@hp.com \
    --cc=xen-devel@lists.xensource.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.