From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Migration and CPU type?
Date: Wed, 15 Feb 2006 15:50:56 -0800 [thread overview]
Message-ID: <43F3BE60.1040901@hp.com> (raw)
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?)
Thanks,
John Byrne
next reply other threads:[~2006-02-15 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 23:50 John Byrne [this message]
2006-02-16 18:25 ` Migration and CPU type? Anthony Liguori
-- 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=43F3BE60.1040901@hp.com \
--to=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.