From: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
To: xen-devel@lists.xensource.comxen-devel@lists.xensource.com
Cc: LAURENT VIVIER <Laurent.Vivier@bull.net>,
JEAN-PIERRE DION <Jean-Pierre.Dion@bull.net>
Subject: VMX disabled by Feature Control MSR
Date: Wed, 14 Jun 2006 13:45:49 +0200 [thread overview]
Message-ID: <20060614134549.2b6e965d@localhost.localdomain> (raw)
Hello,
I already posted a message about this problem on this mailing list but
I went more deeply in the analysis of the problem and I'd like to have
your opinion.
The problem is: I have a processor (pentium D) that supports the VT
technology but when I boot Xen I have the following message:
(XEN) VMX disabled by Feature Control MSR.
Here is how I understand that. Xen is using the CPUID instruction to
identify the processor functionality. This is done in
arch/x86/hvm/vmx/vmx.c:start_vmx(). As VMXON is controlled by the
IA32_FEATURE_CONTROL we must test the lock bit (bit0) and the bit2. I
found in the intel documentation that if the bit2 is clear, VMXON
causes a general-protection exeption. In our case, we stop the
start_vmx() function and display the message VMX disabled by feature
control MSR.
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?
Thanks for your help,
Guillaume
next reply other threads:[~2006-06-14 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:45 Guillaume Thouvenin [this message]
2006-06-14 12:35 ` VMX disabled by Feature Control MSR Guillaume Thouvenin
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=20060614134549.2b6e965d@localhost.localdomain \
--to=guillaume.thouvenin@bull.net \
--cc=Jean-Pierre.Dion@bull.net \
--cc=Laurent.Vivier@bull.net \
--cc=xen-devel@lists.xensource.comxen-devel \
/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.