From: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: LAURENT VIVIER <Laurent.Vivier@bull.net>,
JEAN-PIERRE DION <Jean-Pierre.Dion@bull.net>
Subject: Re: VMX disabled by Feature Control MSR
Date: Wed, 14 Jun 2006 14:35:02 +0200 [thread overview]
Message-ID: <20060614143502.0e7d2289@localhost.localdomain> (raw)
In-Reply-To: <20060614134549.2b6e965d@localhost.localdomain>
On Wed, 14 Jun 2006 13:45:49 +0200
Guillaume Thouvenin <guillaume.thouvenin@bull.net> wrote:
> Thus my question is: What to do to set the bit 2 of the
> IA32_FEATURE_CONTROL to 1? Is it only possible by using the option in
> the BIOS menu (and it's not present in mine) or is it possible to set it
> to 1 before switching in protected mode when Xen is booting. For exemple
> somwhere in arch/x86/boot/x86_64.S?
In fact the problem is how to set the lock bit to 0. In the following
code found in arch/x86/hvm/vmx/vmx.c :
start_vmx() {
...
if (eax & IA32_FEATURE_CONTROL_MSR_LOCK) {
if ((eax & IA32_FEATURE_CONTROL_MSR_ENABLE_VMXON) == 0x0) {
printk("VMX disabled by Feature Control MSR.\n");
return 0;
}
}
else {
wrmsr(IA32_FEATURE_CONTROL_MSR,
IA32_FEATURE_CONTROL_MSR_LOCK |
IA32_FEATURE_CONTROL_MSR_ENABLE_VMXON, 0);
}
...
If the "VMX disabled..." message is displayed, it means that the lock
bit is set to 1. Otherwise we set bit2 to 1. If I try to clear it while
it is set it causes a general-protection fault. Is it possible to modify
before Xen switches from real mode to protected mode?
I will try to modify the arch/x86/boot/x86_64.S
Regards,
Guillaume
next prev parent reply other threads:[~2006-06-14 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:45 VMX disabled by Feature Control MSR Guillaume Thouvenin
2006-06-14 12:35 ` Guillaume Thouvenin [this message]
2006-06-14 12:47 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-06-14 18:26 Kamble, Nitin A
2006-06-15 9:11 ` Jean-Pierre Dion
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=20060614143502.0e7d2289@localhost.localdomain \
--to=guillaume.thouvenin@bull.net \
--cc=Jean-Pierre.Dion@bull.net \
--cc=Laurent.Vivier@bull.net \
--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.