From: David Lively <dlively@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] [HVM] fix 64-bit hvm guest migration
Date: Wed, 10 Oct 2007 17:14:18 -0400 [thread overview]
Message-ID: <470D40AA.9010700@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hi -
We (well, Robert) just (earlier today) noticed we couldn't migrate
64-bit guests with the 3.1.1 and unstable hypervisors. The culprit was
a too-strict test on guest EFER bits, trivially fixed by the following
patch, which applies to both unstable and 3.1.1. Sorry we didn't catch
this before today ...
Dave
The sanity check for ctxt.msr_efer used to fail when EFER_LMA was set.
This prevent migration of 64-bit guests.
Signed-off-by: David Lively <dlively@virtualiron.com>
Signed-off-by: Robert Phillips <rphillips@virtualiron.com>
[-- Attachment #2: xen-hvm-load-efer-test.patch --]
[-- Type: text/x-patch, Size: 615 bytes --]
diff -r e56402b6e155 xen/arch/x86/hvm/hvm.c
--- a/xen/arch/x86/hvm/hvm.c Wed Oct 10 11:37:02 2007 -0400
+++ b/xen/arch/x86/hvm/hvm.c Wed Oct 10 11:37:02 2007 -0400
@@ -389,8 +389,7 @@ static int hvm_load_cpu_ctxt(struct doma
ctxt.msr_efer);
return -EINVAL;
}
-
- if ( (ctxt.msr_efer & ~(EFER_LME | EFER_NX | EFER_SCE)) ||
+ if ( (ctxt.msr_efer & ~(EFER_LME | EFER_LMA | EFER_NX | EFER_SCE)) ||
((sizeof(long) != 8) && (ctxt.msr_efer & EFER_LME)) ||
(!cpu_has_nx && (ctxt.msr_efer & EFER_NX)) ||
(!cpu_has_syscall && (ctxt.msr_efer & EFER_SCE)) ||
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-10-10 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 21:14 David Lively [this message]
2007-10-11 7:15 ` [PATCH] [HVM] fix 64-bit hvm guest migration Keir Fraser
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=470D40AA.9010700@virtualiron.com \
--to=dlively@virtualiron.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.