From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM entry failed, hardware error
Date: Sun, 03 Jun 2012 15:04:17 +0200 [thread overview]
Message-ID: <4FCB60D1.2070509@gmx.de> (raw)
In-Reply-To: <4FCB59A2.4020008@redhat.com>
On 03.06.2012 14:33, Avi Kivity wrote:
> You can run vmxcap [1] and see.
Ah, I forgot to attach the output of vmxcap, which might be of interest.
First the host where it does not work:
pin-based controls
External interrupt exiting yes
NMI exiting yes
Virtual NMIs yes
Activate VMX-preemption timer no
primary processor-based controls
Interrupt window exiting yes
Use TSC offsetting yes
HLT exiting yes
INVLPG exiting yes
MWAIT exiting yes
RDPMC exiting yes
RDTSC exiting yes
CR3-load exiting forced
CR3-store exiting forced
CR8-load exiting yes
CR8-store exiting yes
Use TPR shadow yes
NMI-window exiting yes
MOV-DR exiting yes
Unconditional I/O exiting yes
Use I/O bitmaps yes
Monitor trap flag no
Use MSR bitmaps yes
MONITOR exiting yes
PAUSE exiting yes
Activate secondary control yes
secondary processor-based controls
Virtualize APIC accesses yes
Enable EPT no
Descriptor-table exiting no
Virtualize x2APIC mode no
Enable VPID no
WBINVD exiting yes
Unrestricted guest no
PAUSE-loop exiting no
VM-Exit controls
Save debug controls forced
Host address-space size yes
Load IA32_PERF_GLOBAL_CTRL yes
Acknowledge interrupt on exit yes
Save IA32_PAT no
Load IA32_PAT no
Save IA32_EFER no
Load IA32_EFER no
Save VMX-preemption timer value no
VM-Entry controls
Load debug controls forced
IA-64 mode guest yes
Entry to SMM yes
Deactivate dual-monitor treatment yes
Load IA32_PERF_GLOBAL_CTRL yes
Load IA32_PAT no
Load IA32_EFER no
Miscellaneous data
VMX-preemption timer scale (log2) 0
Store EFER.LMA into IA-32e mode guest control no
HLT activity state yes
Shutdown activity state yes
Wait-for-SIPI activity state yes
Number of CR3-target values 4
MSR-load/store count recommenation 0
MSEG revision identifier 0
VPID and EPT capabilities
Execute-only EPT translations no
Page-walk length 4 no
Paging-structure memory type UC no
Paging-structure memory type WB no
2MB EPT pages no
1GB EPT pages no
INVEPT supported no
Single-context INVEPT no
All-context INVEPT no
INVVPID supported no
Individual-address INVVPID no
Single-context INVVPID no
All-context INVVPID no
Single-context-retaining-globals INVVPID no
Then the one where it does:
pin-based controls
External interrupt exiting yes
NMI exiting yes
Virtual NMIs yes
Activate VMX-preemption timer yes
primary processor-based controls
Interrupt window exiting yes
Use TSC offsetting yes
HLT exiting yes
INVLPG exiting yes
MWAIT exiting yes
RDPMC exiting yes
RDTSC exiting yes
CR3-load exiting default
CR3-store exiting default
CR8-load exiting yes
CR8-store exiting yes
Use TPR shadow yes
NMI-window exiting yes
MOV-DR exiting yes
Unconditional I/O exiting yes
Use I/O bitmaps yes
Monitor trap flag yes
Use MSR bitmaps yes
MONITOR exiting yes
PAUSE exiting yes
Activate secondary control yes
secondary processor-based controls
Virtualize APIC accesses yes
Enable EPT yes
Descriptor-table exiting yes
Virtualize x2APIC mode yes
Enable VPID yes
WBINVD exiting yes
Unrestricted guest yes
PAUSE-loop exiting no
VM-Exit controls
Save debug controls default
Host address-space size yes
Load IA32_PERF_GLOBAL_CTRL yes
Acknowledge interrupt on exit yes
Save IA32_PAT yes
Load IA32_PAT yes
Save IA32_EFER yes
Load IA32_EFER yes
Save VMX-preemption timer value yes
VM-Entry controls
Load debug controls forced
IA-64 mode guest yes
Entry to SMM yes
Deactivate dual-monitor treatment yes
Load IA32_PERF_GLOBAL_CTRL yes
Load IA32_PAT yes
Load IA32_EFER yes
Miscellaneous data
VMX-preemption timer scale (log2) 5
Store EFER.LMA into IA-32e mode guest control yes
HLT activity state yes
Shutdown activity state yes
Wait-for-SIPI activity state yes
Number of CR3-target values 4
MSR-load/store count recommenation 0
MSEG revision identifier 0
VPID and EPT capabilities
Execute-only EPT translations yes
Page-walk length 4 yes
Paging-structure memory type UC yes
Paging-structure memory type WB yes
2MB EPT pages yes
1GB EPT pages no
INVEPT supported yes
Single-context INVEPT yes
All-context INVEPT yes
INVVPID supported yes
Individual-address INVVPID yes
Single-context INVVPID yes
All-context INVVPID yes
Single-context-retaining-globals INVVPID yes
Best regards,
Joe
prev parent reply other threads:[~2012-06-03 13:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 12:18 KVM entry failed, hardware error Johannes Bauer
2012-06-03 12:33 ` Avi Kivity
2012-06-03 13:01 ` Johannes Bauer
2012-06-03 13:43 ` Avi Kivity
2012-06-03 16:25 ` Johannes Bauer
2012-06-04 8:53 ` Gleb Natapov
2012-06-04 8:56 ` Avi Kivity
2012-06-04 18:28 ` Johannes Bauer
2012-06-04 18:32 ` Johannes Bauer
2012-06-05 13:59 ` David Ahern
2012-06-06 18:19 ` Johannes Bauer
2012-06-06 15:53 ` Avi Kivity
2012-06-06 18:07 ` Johannes Bauer
2012-06-07 7:12 ` Avi Kivity
2012-06-07 10:03 ` Johannes Bauer
2012-06-07 10:54 ` Avi Kivity
2012-06-07 14:52 ` Avi Kivity
2012-06-07 15:39 ` Johannes Bauer
2012-06-07 17:25 ` Avi Kivity
2012-06-07 19:14 ` Johannes Bauer
2012-06-10 15:19 ` Avi Kivity
2012-06-12 10:23 ` Johannes Bauer
2012-06-12 10:45 ` Avi Kivity
2012-06-07 19:46 ` Johannes Bauer
2012-06-07 19:54 ` Johannes Bauer
2012-06-03 13:04 ` Johannes Bauer [this message]
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=4FCB60D1.2070509@gmx.de \
--to=dfnsonfsduifb@gmx.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox