* memtest 4.20+ does not work with -cpu host
@ 2012-08-22 15:06 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-08-22 15:06 UTC (permalink / raw)
To: qemu-devel, kvm
Hi,
has anyone ever tested to run memtest with -cpu host flag passed to
qemu-kvm?
For me it resets when probing the chipset. With -cpu qemu64 it works
just fine.
Maybe this is specific to memtest, but it might be sth that can happen
in other
applications to.
Any thoughts?
Thanks,
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-08-22 15:06 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-08-22 15:06 UTC (permalink / raw)
To: qemu-devel, kvm
Hi,
has anyone ever tested to run memtest with -cpu host flag passed to
qemu-kvm?
For me it resets when probing the chipset. With -cpu qemu64 it works
just fine.
Maybe this is specific to memtest, but it might be sth that can happen
in other
applications to.
Any thoughts?
Thanks,
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-08-22 15:06 ` [Qemu-devel] " Peter Lieven
@ 2012-09-06 14:58 ` Avi Kivity
-1 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-06 14:58 UTC (permalink / raw)
To: Peter Lieven; +Cc: qemu-devel, kvm
On 08/22/2012 06:06 PM, Peter Lieven wrote:
> Hi,
>
> has anyone ever tested to run memtest with -cpu host flag passed to
> qemu-kvm?
> For me it resets when probing the chipset. With -cpu qemu64 it works
> just fine.
>
> Maybe this is specific to memtest, but it might be sth that can happen
> in other
> applications to.
>
> Any thoughts?
Try to identify the cpu flag that causes this by removing them
successively (-cpu host,-flag...). Alternatively capture a trace
(http://www.linux-kvm.org/page/Tracing) look for TRIPLE_FAULT (Intel),
and post the few hundred lines preceding it.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-06 14:58 ` Avi Kivity
0 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-06 14:58 UTC (permalink / raw)
To: Peter Lieven; +Cc: qemu-devel, kvm
On 08/22/2012 06:06 PM, Peter Lieven wrote:
> Hi,
>
> has anyone ever tested to run memtest with -cpu host flag passed to
> qemu-kvm?
> For me it resets when probing the chipset. With -cpu qemu64 it works
> just fine.
>
> Maybe this is specific to memtest, but it might be sth that can happen
> in other
> applications to.
>
> Any thoughts?
Try to identify the cpu flag that causes this by removing them
successively (-cpu host,-flag...). Alternatively capture a trace
(http://www.linux-kvm.org/page/Tracing) look for TRIPLE_FAULT (Intel),
and post the few hundred lines preceding it.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-06 14:58 ` [Qemu-devel] " Avi Kivity
@ 2012-09-10 11:06 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:06 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel, kvm
On 09/06/12 16:58, Avi Kivity wrote:
> On 08/22/2012 06:06 PM, Peter Lieven wrote:
>> Hi,
>>
>> has anyone ever tested to run memtest with -cpu host flag passed to
>> qemu-kvm?
>> For me it resets when probing the chipset. With -cpu qemu64 it works
>> just fine.
>>
>> Maybe this is specific to memtest, but it might be sth that can happen
>> in other
>> applications to.
>>
>> Any thoughts?
> Try to identify the cpu flag that causes this by removing them
> successively (-cpu host,-flag...). Alternatively capture a trace
> (http://www.linux-kvm.org/page/Tracing) look for TRIPLE_FAULT (Intel),
> and post the few hundred lines preceding it.
>
Here we go:
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EXCEPTION_NMI
rip 0xd185 info 0 80000307
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: load
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: unload
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfe0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfe size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EXCEPTION_NMI
rip 0xd185 info 0 80000307
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: load
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: unload
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb873c
gpa 0xb873c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb873c val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb873e
gpa 0xb873e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb873e val 0x66
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8740
gpa 0xb8740 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8740 val 0x66
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d4
gpa 0xb83d4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d4 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d6
gpa 0xb83d6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d6 val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d8
gpa 0xb83d8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d8 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83da
gpa 0xb83da Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83da val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83dc
gpa 0xb83dc Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83dc val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83de
gpa 0xb83de Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83de val 0x49
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e0
gpa 0xb83e0 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e0 val 0x4d
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e2
gpa 0xb83e2 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e2 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e4
gpa 0xb83e4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e4 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e6
gpa 0xb83e6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e6 val 0x33
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e8
gpa 0xb83e8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e8 val 0x32
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ea
gpa 0xb83ea Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ea val 0x6e
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ec
gpa 0xb83ec Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ec val 0x6d
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ee
gpa 0xb83ee Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ee val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f0
gpa 0xb83f0 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f0 val 0x28
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f2
gpa 0xb83f2 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f2 val 0x45
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f4
gpa 0xb83f4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f4 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f6
gpa 0xb83f6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f6 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f8
gpa 0xb83f8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f8 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fa
gpa 0xb83fa Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fa val 0x3a
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fc
gpa 0xb83fc Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fc val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fe
gpa 0xb83fe Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fe val 0x44
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8400
gpa 0xb8400 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8400 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8402
gpa 0xb8402 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8402 val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8404
gpa 0xb8404 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8404 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8406
gpa 0xb8406 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8406 val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8408
gpa 0xb8408 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8408 val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840a
gpa 0xb840a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840a val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840c
gpa 0xb840c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840c val 0x2f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840e
gpa 0xb840e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840e val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8410
gpa 0xb8410 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8410 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8412
gpa 0xb8412 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8412 val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8414
gpa 0xb8414 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8414 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8416
gpa 0xb8416 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8416 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8418
gpa 0xb8418 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8418 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841a
gpa 0xb841a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841a val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841c
gpa 0xb841c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841c val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841e
gpa 0xb841e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841e val 0x29
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8420
gpa 0xb8420 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8420 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8422
gpa 0xb8422 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8422 val 0x53
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8424
gpa 0xb8424 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8424 val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8426
gpa 0xb8426 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8426 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8428
gpa 0xb8428 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8428 val 0x75
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842a
gpa 0xb842a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842a val 0x62
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842c
gpa 0xb842c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842c val 0x2b
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842e
gpa 0xb842e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842e val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0x9190 info 640048 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=37264 csbase=0 len=2 insn=äd¨\x01uJ‹ƒÌ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0x64 size
1 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
0x11478 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
rip 0x11478 info 0 0
Thanks,
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 11:06 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:06 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel, kvm
On 09/06/12 16:58, Avi Kivity wrote:
> On 08/22/2012 06:06 PM, Peter Lieven wrote:
>> Hi,
>>
>> has anyone ever tested to run memtest with -cpu host flag passed to
>> qemu-kvm?
>> For me it resets when probing the chipset. With -cpu qemu64 it works
>> just fine.
>>
>> Maybe this is specific to memtest, but it might be sth that can happen
>> in other
>> applications to.
>>
>> Any thoughts?
> Try to identify the cpu flag that causes this by removing them
> successively (-cpu host,-flag...). Alternatively capture a trace
> (http://www.linux-kvm.org/page/Tracing) look for TRIPLE_FAULT (Intel),
> and post the few hundred lines preceding it.
>
Here we go:
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EXCEPTION_NMI
rip 0xd185 info 0 80000307
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: load
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: unload
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfe0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfe size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EXCEPTION_NMI
rip 0xd185 info 0 80000307
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: load
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_fpu: unload
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc60 info cf80003 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_write at 0xcf8
size 4 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0xcc29 info cfc0009 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=52265 csbase=0 len=2 insn=fí%ÿÿ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0xcfc size
2 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb873c
gpa 0xb873c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb873c val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb873e
gpa 0xb873e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb873e val 0x66
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8740
gpa 0xb8740 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8740 val 0x66
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d4
gpa 0xb83d4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d4 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d6
gpa 0xb83d6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d6 val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83d8
gpa 0xb83d8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83d8 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83da
gpa 0xb83da Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83da val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83dc
gpa 0xb83dc Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83dc val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83de
gpa 0xb83de Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83de val 0x49
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e0
gpa 0xb83e0 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e0 val 0x4d
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e2
gpa 0xb83e2 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e2 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e4
gpa 0xb83e4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e4 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e6
gpa 0xb83e6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e6 val 0x33
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83e8
gpa 0xb83e8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83e8 val 0x32
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ea
gpa 0xb83ea Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ea val 0x6e
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ec
gpa 0xb83ec Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ec val 0x6d
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83ee
gpa 0xb83ee Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83ee val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f0
gpa 0xb83f0 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f0 val 0x28
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f2
gpa 0xb83f2 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f2 val 0x45
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f4
gpa 0xb83f4 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f4 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f6
gpa 0xb83f6 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f6 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83f8
gpa 0xb83f8 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83f8 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fa
gpa 0xb83fa Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fa val 0x3a
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fc
gpa 0xb83fc Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fc val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb83fe
gpa 0xb83fe Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb83fe val 0x44
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8400
gpa 0xb8400 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8400 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8402
gpa 0xb8402 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8402 val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8404
gpa 0xb8404 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8404 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8406
gpa 0xb8406 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8406 val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8408
gpa 0xb8408 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8408 val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840a
gpa 0xb840a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840a val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840c
gpa 0xb840c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840c val 0x2f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb840e
gpa 0xb840e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb840e val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8410
gpa 0xb8410 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8410 val 0x43
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8412
gpa 0xb8412 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8412 val 0x6f
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8414
gpa 0xb8414 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8414 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8416
gpa 0xb8416 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8416 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8418
gpa 0xb8418 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8418 val 0x65
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841a
gpa 0xb841a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841a val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841c
gpa 0xb841c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841c val 0x74
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb841e
gpa 0xb841e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb841e val 0x29
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8420
gpa 0xb8420 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8420 val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8422
gpa 0xb8422 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8422 val 0x53
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8424
gpa 0xb8424 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8424 val 0x63
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8426
gpa 0xb8426 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8426 val 0x72
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb8428
gpa 0xb8428 Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb8428 val 0x75
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842a
gpa 0xb842a Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842a val 0x62
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842c
gpa 0xb842c Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842c val 0x2b
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason EPT_MISCONFIG
rip 0x86e0 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=34528 csbase=0 len=3 insn=ˆ\x14F@Š\x14\x01„Òuõ‰L$\b\x05 flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: vcpu_match_mmio: gva 0xb842e
gpa 0xb842e Write GPA
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_mmio: mmio write len 1 gpa
0xb842e val 0x20
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason IO_INSTRUCTION
rip 0x9190 info 640048 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_emulate_insn: [FAILED TO
PARSE] rip=37264 csbase=0 len=2 insn=äd¨\x01uJ‹ƒÌ flags=5 failed=0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_pio: pio_read at 0x64 size
1 count 1
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
0x11478 info 0 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
rip 0x11478 info 0 0
Thanks,
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 11:06 ` [Qemu-devel] " Peter Lieven
@ 2012-09-10 11:29 ` Paolo Bonzini
-1 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-10 11:29 UTC (permalink / raw)
To: Peter Lieven; +Cc: Avi Kivity, kvm, qemu-devel
Il 10/09/2012 13:06, Peter Lieven ha scritto:
>
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
> 0x11478 info 0 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
> rip 0x11478 info 0 0
Memory controller MSR:
static float getNHMmultiplier(void)
{
unsigned int msr_lo, msr_hi;
float coef;
/* Find multiplier (by MSR) */
/* First, check if Flexible Ratio is Enabled */
rdmsr(0x194, msr_lo, msr_hi);
if((msr_lo >> 16) & 1){
coef = (msr_lo >> 8) & 0xFF;
} else {
rdmsr(0xCE, msr_lo, msr_hi);
coef = (msr_lo >> 8) & 0xFF;
}
return coef;
}
Looks like we need to emulate it since memtest only looks at the cpuid
to detect an integrated memory controller. What does this return for you?
dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 11:29 ` Paolo Bonzini
0 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-10 11:29 UTC (permalink / raw)
To: Peter Lieven; +Cc: Avi Kivity, kvm, qemu-devel
Il 10/09/2012 13:06, Peter Lieven ha scritto:
>
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
> 0x11478 info 0 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
> rip 0x11478 info 0 0
Memory controller MSR:
static float getNHMmultiplier(void)
{
unsigned int msr_lo, msr_hi;
float coef;
/* Find multiplier (by MSR) */
/* First, check if Flexible Ratio is Enabled */
rdmsr(0x194, msr_lo, msr_hi);
if((msr_lo >> 16) & 1){
coef = (msr_lo >> 8) & 0xFF;
} else {
rdmsr(0xCE, msr_lo, msr_hi);
coef = (msr_lo >> 8) & 0xFF;
}
return coef;
}
Looks like we need to emulate it since memtest only looks at the cpuid
to detect an integrated memory controller. What does this return for you?
dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 11:29 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-10 11:47 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:47 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Avi Kivity, qemu-devel, kvm
On 09/10/12 13:29, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo>> 16)& 1){
> coef = (msr_lo>> 8)& 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo>> 8)& 0xFF;
> }
>
> return coef;
> }
>
> Looks like we need to emulate it since memtest only looks at the cpuid
> to detect an integrated memory controller. What does this return for you?
>
> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
I/O error.
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 11:47 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:47 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Avi Kivity, kvm, qemu-devel
On 09/10/12 13:29, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo>> 16)& 1){
> coef = (msr_lo>> 8)& 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo>> 8)& 0xFF;
> }
>
> return coef;
> }
>
> Looks like we need to emulate it since memtest only looks at the cpuid
> to detect an integrated memory controller. What does this return for you?
>
> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
I/O error.
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 11:29 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-10 11:52 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:52 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Avi Kivity, qemu-devel, kvm
On 09/10/12 13:29, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo>> 16)& 1){
> coef = (msr_lo>> 8)& 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo>> 8)& 0xFF;
> }
>
> return coef;
> }
>
> Looks like we need to emulate it since memtest only looks at the cpuid
> to detect an integrated memory controller. What does this return for you?
>
> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
it only works without the skip. but the msr device returns all zeroes.
peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 11:52 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 11:52 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Avi Kivity, kvm, qemu-devel
On 09/10/12 13:29, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo>> 16)& 1){
> coef = (msr_lo>> 8)& 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo>> 8)& 0xFF;
> }
>
> return coef;
> }
>
> Looks like we need to emulate it since memtest only looks at the cpuid
> to detect an integrated memory controller. What does this return for you?
>
> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
it only works without the skip. but the msr device returns all zeroes.
peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 11:29 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-10 12:12 ` Avi Kivity
-1 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-10 12:12 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, qemu-devel, kvm
On 09/10/2012 02:29 PM, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>>
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
>
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo >> 16) & 1){
> coef = (msr_lo >> 8) & 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo >> 8) & 0xFF;
> }
>
> return coef;
> }
>
The SDM only mentions 0x194 as a machine check exception register
(recorded R12).
In the Architectural MSRs (how I love that name) section 18AH-197H are
listed as reserved.
In the Nehalem section they're not there at all.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:12 ` Avi Kivity
0 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-10 12:12 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, qemu-devel, kvm
On 09/10/2012 02:29 PM, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>>
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
>
> Memory controller MSR:
>
> static float getNHMmultiplier(void)
> {
> unsigned int msr_lo, msr_hi;
> float coef;
>
> /* Find multiplier (by MSR) */
> /* First, check if Flexible Ratio is Enabled */
> rdmsr(0x194, msr_lo, msr_hi);
> if((msr_lo >> 16) & 1){
> coef = (msr_lo >> 8) & 0xFF;
> } else {
> rdmsr(0xCE, msr_lo, msr_hi);
> coef = (msr_lo >> 8) & 0xFF;
> }
>
> return coef;
> }
>
The SDM only mentions 0x194 as a machine check exception register
(recorded R12).
In the Architectural MSRs (how I love that name) section 18AH-197H are
listed as reserved.
In the Nehalem section they're not there at all.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 11:52 ` [Qemu-devel] " Peter Lieven
@ 2012-09-10 12:15 ` Paolo Bonzini
-1 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-10 12:15 UTC (permalink / raw)
To: Peter Lieven; +Cc: Avi Kivity, qemu-devel, kvm
Il 10/09/2012 13:52, Peter Lieven ha scritto:
>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> it only works without the skip. but the msr device returns all zeroes.
Hmm, the strange API of the MSR device doesn't work well with dd (dd
skips to 0x194 * 8 because bs is 8. You can try this program:
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
int rdmsr(int fd, long reg)
{
char msg[40];
long long val;
sprintf(msg, "rdmsr(%#x)", reg);
if (pread(fd, &val, 8, reg) < 0) {
perror(msg);
} else {
printf("%s: %#016llx\n", msg, val);
fflush(stdout);
}
}
int main()
{
int fd = open("/dev/cpu/0/msr", O_RDONLY);
if (fd < 0) { perror("open"); exit(1); }
rdmsr(fd, 0x194);
rdmsr(fd, 0xCE);
}
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:15 ` Paolo Bonzini
0 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-10 12:15 UTC (permalink / raw)
To: Peter Lieven; +Cc: Avi Kivity, kvm, qemu-devel
Il 10/09/2012 13:52, Peter Lieven ha scritto:
>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> it only works without the skip. but the msr device returns all zeroes.
Hmm, the strange API of the MSR device doesn't work well with dd (dd
skips to 0x194 * 8 because bs is 8. You can try this program:
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
int rdmsr(int fd, long reg)
{
char msg[40];
long long val;
sprintf(msg, "rdmsr(%#x)", reg);
if (pread(fd, &val, 8, reg) < 0) {
perror(msg);
} else {
printf("%s: %#016llx\n", msg, val);
fflush(stdout);
}
}
int main()
{
int fd = open("/dev/cpu/0/msr", O_RDONLY);
if (fd < 0) { perror("open"); exit(1); }
rdmsr(fd, 0x194);
rdmsr(fd, 0xCE);
}
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 12:15 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-10 12:21 ` Gleb Natapov
-1 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-10 12:21 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, Avi Kivity, qemu-devel, kvm
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
> Il 10/09/2012 13:52, Peter Lieven ha scritto:
> >> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> >> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> > it only works without the skip. but the msr device returns all zeroes.
>
> Hmm, the strange API of the MSR device doesn't work well with dd (dd
> skips to 0x194 * 8 because bs is 8. You can try this program:
>
There is rdmsr/wrmsr in msr-tools.
> #include <fcntl.h>
> #include <stdio.h>
> #include <stdlib.h>
>
> int rdmsr(int fd, long reg)
> {
> char msg[40];
> long long val;
> sprintf(msg, "rdmsr(%#x)", reg);
> if (pread(fd, &val, 8, reg) < 0) {
> perror(msg);
> } else {
> printf("%s: %#016llx\n", msg, val);
> fflush(stdout);
> }
> }
>
>
> int main()
> {
> int fd = open("/dev/cpu/0/msr", O_RDONLY);
> if (fd < 0) { perror("open"); exit(1); }
> rdmsr(fd, 0x194);
> rdmsr(fd, 0xCE);
> }
>
> Paolo
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:21 ` Gleb Natapov
0 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-10 12:21 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, Avi Kivity, kvm, qemu-devel
On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
> Il 10/09/2012 13:52, Peter Lieven ha scritto:
> >> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
> >> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
> > it only works without the skip. but the msr device returns all zeroes.
>
> Hmm, the strange API of the MSR device doesn't work well with dd (dd
> skips to 0x194 * 8 because bs is 8. You can try this program:
>
There is rdmsr/wrmsr in msr-tools.
> #include <fcntl.h>
> #include <stdio.h>
> #include <stdlib.h>
>
> int rdmsr(int fd, long reg)
> {
> char msg[40];
> long long val;
> sprintf(msg, "rdmsr(%#x)", reg);
> if (pread(fd, &val, 8, reg) < 0) {
> perror(msg);
> } else {
> printf("%s: %#016llx\n", msg, val);
> fflush(stdout);
> }
> }
>
>
> int main()
> {
> int fd = open("/dev/cpu/0/msr", O_RDONLY);
> if (fd < 0) { perror("open"); exit(1); }
> rdmsr(fd, 0x194);
> rdmsr(fd, 0xCE);
> }
>
> Paolo
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 12:21 ` [Qemu-devel] " Gleb Natapov
@ 2012-09-10 12:29 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 12:29 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, Avi Kivity, qemu-devel, kvm
On 09/10/12 14:21, Gleb Natapov wrote:
> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>> it only works without the skip. but the msr device returns all zeroes.
>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>
> There is rdmsr/wrmsr in msr-tools.
rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
or -cpu qemu64.
peter
>> #include<fcntl.h>
>> #include<stdio.h>
>> #include<stdlib.h>
>>
>> int rdmsr(int fd, long reg)
>> {
>> char msg[40];
>> long long val;
>> sprintf(msg, "rdmsr(%#x)", reg);
>> if (pread(fd,&val, 8, reg)< 0) {
>> perror(msg);
>> } else {
>> printf("%s: %#016llx\n", msg, val);
>> fflush(stdout);
>> }
>> }
>>
>>
>> int main()
>> {
>> int fd = open("/dev/cpu/0/msr", O_RDONLY);
>> if (fd< 0) { perror("open"); exit(1); }
>> rdmsr(fd, 0x194);
>> rdmsr(fd, 0xCE);
>> }
>>
>> Paolo
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:29 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 12:29 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, Avi Kivity, kvm, qemu-devel
On 09/10/12 14:21, Gleb Natapov wrote:
> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>> it only works without the skip. but the msr device returns all zeroes.
>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>
> There is rdmsr/wrmsr in msr-tools.
rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
or -cpu qemu64.
peter
>> #include<fcntl.h>
>> #include<stdio.h>
>> #include<stdlib.h>
>>
>> int rdmsr(int fd, long reg)
>> {
>> char msg[40];
>> long long val;
>> sprintf(msg, "rdmsr(%#x)", reg);
>> if (pread(fd,&val, 8, reg)< 0) {
>> perror(msg);
>> } else {
>> printf("%s: %#016llx\n", msg, val);
>> fflush(stdout);
>> }
>> }
>>
>>
>> int main()
>> {
>> int fd = open("/dev/cpu/0/msr", O_RDONLY);
>> if (fd< 0) { perror("open"); exit(1); }
>> rdmsr(fd, 0x194);
>> rdmsr(fd, 0xCE);
>> }
>>
>> Paolo
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 12:29 ` [Qemu-devel] " Peter Lieven
@ 2012-09-10 12:32 ` Avi Kivity
-1 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-10 12:32 UTC (permalink / raw)
To: Peter Lieven; +Cc: Gleb Natapov, Paolo Bonzini, qemu-devel, kvm
On 09/10/2012 03:29 PM, Peter Lieven wrote:
> On 09/10/12 14:21, Gleb Natapov wrote:
>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>> it only works without the skip. but the msr device returns all zeroes.
>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>
>> There is rdmsr/wrmsr in msr-tools.
> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
> or -cpu qemu64.
On the host.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:32 ` Avi Kivity
0 siblings, 0 replies; 42+ messages in thread
From: Avi Kivity @ 2012-09-10 12:32 UTC (permalink / raw)
To: Peter Lieven; +Cc: Paolo Bonzini, qemu-devel, Gleb Natapov, kvm
On 09/10/2012 03:29 PM, Peter Lieven wrote:
> On 09/10/12 14:21, Gleb Natapov wrote:
>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>> it only works without the skip. but the msr device returns all zeroes.
>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>
>> There is rdmsr/wrmsr in msr-tools.
> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
> or -cpu qemu64.
On the host.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 12:32 ` [Qemu-devel] " Avi Kivity
@ 2012-09-10 12:38 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 12:38 UTC (permalink / raw)
To: Avi Kivity; +Cc: Paolo Bonzini, qemu-devel, Gleb Natapov, kvm
On 09/10/12 14:32, Avi Kivity wrote:
> On 09/10/2012 03:29 PM, Peter Lieven wrote:
>> On 09/10/12 14:21, Gleb Natapov wrote:
>>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>>> it only works without the skip. but the msr device returns all zeroes.
>>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>>
>>> There is rdmsr/wrmsr in msr-tools.
>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>> or -cpu qemu64.
> On the host.
aaah ok:
#rdmsr -0 0x194
0000000000011100
#rdmsr -0 0xce
00000c0004011103
Peter
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-10 12:38 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-10 12:38 UTC (permalink / raw)
To: Avi Kivity; +Cc: Paolo Bonzini, qemu-devel, Gleb Natapov, kvm
On 09/10/12 14:32, Avi Kivity wrote:
> On 09/10/2012 03:29 PM, Peter Lieven wrote:
>> On 09/10/12 14:21, Gleb Natapov wrote:
>>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>>> it only works without the skip. but the msr device returns all zeroes.
>>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>>
>>> There is rdmsr/wrmsr in msr-tools.
>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>> or -cpu qemu64.
> On the host.
aaah ok:
#rdmsr -0 0x194
0000000000011100
#rdmsr -0 0xce
00000c0004011103
Peter
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-10 12:32 ` [Qemu-devel] " Avi Kivity
@ 2012-09-13 7:53 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 7:53 UTC (permalink / raw)
To: Avi Kivity; +Cc: Gleb Natapov, Paolo Bonzini, qemu-devel, kvm
On 10.09.2012 14:32, Avi Kivity wrote:
> On 09/10/2012 03:29 PM, Peter Lieven wrote:
>> On 09/10/12 14:21, Gleb Natapov wrote:
>>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>>> it only works without the skip. but the msr device returns all zeroes.
>>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>>
>>> There is rdmsr/wrmsr in msr-tools.
>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>> or -cpu qemu64.
> On the host.
>
>
did you get my output?
#rdmsr -0 0x194
0000000000011100
#rdmsr -0 0xce
00000c0004011103
cheers,
peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 7:53 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 7:53 UTC (permalink / raw)
To: Avi Kivity; +Cc: Paolo Bonzini, qemu-devel, Gleb Natapov, kvm
On 10.09.2012 14:32, Avi Kivity wrote:
> On 09/10/2012 03:29 PM, Peter Lieven wrote:
>> On 09/10/12 14:21, Gleb Natapov wrote:
>>> On Mon, Sep 10, 2012 at 02:15:49PM +0200, Paolo Bonzini wrote:
>>>> Il 10/09/2012 13:52, Peter Lieven ha scritto:
>>>>>> dd if=/dev/cpu/0/msr skip=$((0x194)) bs=8 count=1 | xxd
>>>>>> dd if=/dev/cpu/0/msr skip=$((0xCE)) bs=8 count=1 | xxd
>>>>> it only works without the skip. but the msr device returns all zeroes.
>>>> Hmm, the strange API of the MSR device doesn't work well with dd (dd
>>>> skips to 0x194 * 8 because bs is 8. You can try this program:
>>>>
>>> There is rdmsr/wrmsr in msr-tools.
>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>> or -cpu qemu64.
> On the host.
>
>
did you get my output?
#rdmsr -0 0x194
0000000000011100
#rdmsr -0 0xce
00000c0004011103
cheers,
peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 7:53 ` [Qemu-devel] " Peter Lieven
@ 2012-09-13 7:55 ` Paolo Bonzini
-1 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-13 7:55 UTC (permalink / raw)
To: Peter Lieven; +Cc: Avi Kivity, Gleb Natapov, qemu-devel, kvm, H. Peter Anvin
Il 13/09/2012 09:53, Peter Lieven ha scritto:
>>>>
>>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>>> or -cpu qemu64.
>> On the host.
>>
>>
> did you get my output?
>
> #rdmsr -0 0x194
> 0000000000011100
> #rdmsr -0 0xce
> 00000c0004011103
Yes, that can help implementing it in KVM. But without a spec to
understand what the bits actually mean, it's just as risky...
Peter, do you have any idea where to get the spec of the memory
controller MSRs in Nehalem and newer processors? Apparently, memtest is
using them (and in particular 0x194) to find the speed of the FSB, or
something like that.
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 7:55 ` Paolo Bonzini
0 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-13 7:55 UTC (permalink / raw)
To: Peter Lieven; +Cc: kvm, H. Peter Anvin, Avi Kivity, Gleb Natapov, qemu-devel
Il 13/09/2012 09:53, Peter Lieven ha scritto:
>>>>
>>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
>>> or -cpu qemu64.
>> On the host.
>>
>>
> did you get my output?
>
> #rdmsr -0 0x194
> 0000000000011100
> #rdmsr -0 0xce
> 00000c0004011103
Yes, that can help implementing it in KVM. But without a spec to
understand what the bits actually mean, it's just as risky...
Peter, do you have any idea where to get the spec of the memory
controller MSRs in Nehalem and newer processors? Apparently, memtest is
using them (and in particular 0x194) to find the speed of the FSB, or
something like that.
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 7:55 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-13 7:57 ` Gleb Natapov
-1 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 7:57 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On Thu, Sep 13, 2012 at 09:55:06AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:53, Peter Lieven ha scritto:
> >>>>
> >>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
> >>> or -cpu qemu64.
> >> On the host.
> >>
> >>
> > did you get my output?
> >
> > #rdmsr -0 0x194
> > 0000000000011100
> > #rdmsr -0 0xce
> > 00000c0004011103
>
> Yes, that can help implementing it in KVM. But without a spec to
> understand what the bits actually mean, it's just as risky...
>
> Peter, do you have any idea where to get the spec of the memory
> controller MSRs in Nehalem and newer processors? Apparently, memtest is
> using them (and in particular 0x194) to find the speed of the FSB, or
> something like that.
>
Why would anyone will want to run memtest in a vm? May be just add those
MSRs to ignore list and that's it.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 7:57 ` Gleb Natapov
0 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 7:57 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: H. Peter Anvin, Peter Lieven, Avi Kivity, kvm, qemu-devel
On Thu, Sep 13, 2012 at 09:55:06AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:53, Peter Lieven ha scritto:
> >>>>
> >>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host
> >>> or -cpu qemu64.
> >> On the host.
> >>
> >>
> > did you get my output?
> >
> > #rdmsr -0 0x194
> > 0000000000011100
> > #rdmsr -0 0xce
> > 00000c0004011103
>
> Yes, that can help implementing it in KVM. But without a spec to
> understand what the bits actually mean, it's just as risky...
>
> Peter, do you have any idea where to get the spec of the memory
> controller MSRs in Nehalem and newer processors? Apparently, memtest is
> using them (and in particular 0x194) to find the speed of the FSB, or
> something like that.
>
Why would anyone will want to run memtest in a vm? May be just add those
MSRs to ignore list and that's it.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 7:57 ` [Qemu-devel] " Gleb Natapov
@ 2012-09-13 8:00 ` Paolo Bonzini
-1 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-13 8:00 UTC (permalink / raw)
To: Gleb Natapov; +Cc: H. Peter Anvin, Peter Lieven, Avi Kivity, kvm, qemu-devel
Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>> > >
>>> > > #rdmsr -0 0x194
>>> > > 0000000000011100
>>> > > #rdmsr -0 0xce
>>> > > 00000c0004011103
>> >
>> > Yes, that can help implementing it in KVM. But without a spec to
>> > understand what the bits actually mean, it's just as risky...
>> >
>> > Peter, do you have any idea where to get the spec of the memory
>> > controller MSRs in Nehalem and newer processors? Apparently, memtest is
>> > using them (and in particular 0x194) to find the speed of the FSB, or
>> > something like that.
>> >
> Why would anyone will want to run memtest in a vm? May be just add those
> MSRs to ignore list and that's it.
>From the output it looks like it's basically a list of bits. Returning
something sensible is better, same as for the speed scaling MSRs.
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 8:00 ` Paolo Bonzini
0 siblings, 0 replies; 42+ messages in thread
From: Paolo Bonzini @ 2012-09-13 8:00 UTC (permalink / raw)
To: Gleb Natapov; +Cc: H. Peter Anvin, Peter Lieven, Avi Kivity, kvm, qemu-devel
Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>> > >
>>> > > #rdmsr -0 0x194
>>> > > 0000000000011100
>>> > > #rdmsr -0 0xce
>>> > > 00000c0004011103
>> >
>> > Yes, that can help implementing it in KVM. But without a spec to
>> > understand what the bits actually mean, it's just as risky...
>> >
>> > Peter, do you have any idea where to get the spec of the memory
>> > controller MSRs in Nehalem and newer processors? Apparently, memtest is
>> > using them (and in particular 0x194) to find the speed of the FSB, or
>> > something like that.
>> >
> Why would anyone will want to run memtest in a vm? May be just add those
> MSRs to ignore list and that's it.
>From the output it looks like it's basically a list of bits. Returning
something sensible is better, same as for the speed scaling MSRs.
Paolo
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 8:00 ` [Qemu-devel] " Paolo Bonzini
@ 2012-09-13 8:05 ` Gleb Natapov
-1 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 8:05 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Lieven, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>> > >
> >>> > > #rdmsr -0 0x194
> >>> > > 0000000000011100
> >>> > > #rdmsr -0 0xce
> >>> > > 00000c0004011103
> >> >
> >> > Yes, that can help implementing it in KVM. But without a spec to
> >> > understand what the bits actually mean, it's just as risky...
> >> >
> >> > Peter, do you have any idea where to get the spec of the memory
> >> > controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >> > using them (and in particular 0x194) to find the speed of the FSB, or
> >> > something like that.
> >> >
> > Why would anyone will want to run memtest in a vm? May be just add those
> > MSRs to ignore list and that's it.
>
> >From the output it looks like it's basically a list of bits. Returning
> something sensible is better, same as for the speed scaling MSRs.
>
Everything is list of bits in computers :) At least 0xce is documented in SDM.
It cannot be implemented in a migration safe manner.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 8:05 ` Gleb Natapov
0 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 8:05 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: H. Peter Anvin, Peter Lieven, Avi Kivity, kvm, qemu-devel
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>> > >
> >>> > > #rdmsr -0 0x194
> >>> > > 0000000000011100
> >>> > > #rdmsr -0 0xce
> >>> > > 00000c0004011103
> >> >
> >> > Yes, that can help implementing it in KVM. But without a spec to
> >> > understand what the bits actually mean, it's just as risky...
> >> >
> >> > Peter, do you have any idea where to get the spec of the memory
> >> > controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >> > using them (and in particular 0x194) to find the speed of the FSB, or
> >> > something like that.
> >> >
> > Why would anyone will want to run memtest in a vm? May be just add those
> > MSRs to ignore list and that's it.
>
> >From the output it looks like it's basically a list of bits. Returning
> something sensible is better, same as for the speed scaling MSRs.
>
Everything is list of bits in computers :) At least 0xce is documented in SDM.
It cannot be implemented in a migration safe manner.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 8:05 ` [Qemu-devel] " Gleb Natapov
@ 2012-09-13 12:05 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 12:05 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On 13.09.2012 10:05, Gleb Natapov wrote:
> On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
>> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>>>>>> #rdmsr -0 0x194
>>>>>>> 0000000000011100
>>>>>>> #rdmsr -0 0xce
>>>>>>> 00000c0004011103
>>>>> Yes, that can help implementing it in KVM. But without a spec to
>>>>> understand what the bits actually mean, it's just as risky...
>>>>>
>>>>> Peter, do you have any idea where to get the spec of the memory
>>>>> controller MSRs in Nehalem and newer processors? Apparently, memtest is
>>>>> using them (and in particular 0x194) to find the speed of the FSB, or
>>>>> something like that.
>>>>>
>>> Why would anyone will want to run memtest in a vm? May be just add those
>>> MSRs to ignore list and that's it.
>> >From the output it looks like it's basically a list of bits. Returning
>> something sensible is better, same as for the speed scaling MSRs.
>>
> Everything is list of bits in computers :) At least 0xce is documented in SDM.
> It cannot be implemented in a migration safe manner.
What do you suggest just say memtest does not work?
I am wondering why it is working with -cpu qemu64.
Peter
>
> --
> Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 12:05 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 12:05 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, H. Peter Anvin, Avi Kivity, kvm, qemu-devel
On 13.09.2012 10:05, Gleb Natapov wrote:
> On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
>> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>>>>>> #rdmsr -0 0x194
>>>>>>> 0000000000011100
>>>>>>> #rdmsr -0 0xce
>>>>>>> 00000c0004011103
>>>>> Yes, that can help implementing it in KVM. But without a spec to
>>>>> understand what the bits actually mean, it's just as risky...
>>>>>
>>>>> Peter, do you have any idea where to get the spec of the memory
>>>>> controller MSRs in Nehalem and newer processors? Apparently, memtest is
>>>>> using them (and in particular 0x194) to find the speed of the FSB, or
>>>>> something like that.
>>>>>
>>> Why would anyone will want to run memtest in a vm? May be just add those
>>> MSRs to ignore list and that's it.
>> >From the output it looks like it's basically a list of bits. Returning
>> something sensible is better, same as for the speed scaling MSRs.
>>
> Everything is list of bits in computers :) At least 0xce is documented in SDM.
> It cannot be implemented in a migration safe manner.
What do you suggest just say memtest does not work?
I am wondering why it is working with -cpu qemu64.
Peter
>
> --
> Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 12:05 ` [Qemu-devel] " Peter Lieven
@ 2012-09-13 12:42 ` Gleb Natapov
-1 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 12:42 UTC (permalink / raw)
To: Peter Lieven; +Cc: Paolo Bonzini, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> On 13.09.2012 10:05, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> >>Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>>>>>>#rdmsr -0 0x194
> >>>>>>>0000000000011100
> >>>>>>>#rdmsr -0 0xce
> >>>>>>>00000c0004011103
> >>>>>Yes, that can help implementing it in KVM. But without a spec to
> >>>>>understand what the bits actually mean, it's just as risky...
> >>>>>
> >>>>>Peter, do you have any idea where to get the spec of the memory
> >>>>>controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >>>>>using them (and in particular 0x194) to find the speed of the FSB, or
> >>>>>something like that.
> >>>>>
> >>>Why would anyone will want to run memtest in a vm? May be just add those
> >>>MSRs to ignore list and that's it.
> >>>From the output it looks like it's basically a list of bits. Returning
> >>something sensible is better, same as for the speed scaling MSRs.
> >>
> >Everything is list of bits in computers :) At least 0xce is documented in SDM.
> >It cannot be implemented in a migration safe manner.
> What do you suggest just say memtest does not work?
Why do you want to run it in a guest?
> I am wondering why it is working with -cpu qemu64.
>
Because memtest has different code for different cpu models.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 12:42 ` Gleb Natapov
0 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 12:42 UTC (permalink / raw)
To: Peter Lieven; +Cc: Paolo Bonzini, H. Peter Anvin, Avi Kivity, kvm, qemu-devel
On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> On 13.09.2012 10:05, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> >>Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>>>>>>#rdmsr -0 0x194
> >>>>>>>0000000000011100
> >>>>>>>#rdmsr -0 0xce
> >>>>>>>00000c0004011103
> >>>>>Yes, that can help implementing it in KVM. But without a spec to
> >>>>>understand what the bits actually mean, it's just as risky...
> >>>>>
> >>>>>Peter, do you have any idea where to get the spec of the memory
> >>>>>controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >>>>>using them (and in particular 0x194) to find the speed of the FSB, or
> >>>>>something like that.
> >>>>>
> >>>Why would anyone will want to run memtest in a vm? May be just add those
> >>>MSRs to ignore list and that's it.
> >>>From the output it looks like it's basically a list of bits. Returning
> >>something sensible is better, same as for the speed scaling MSRs.
> >>
> >Everything is list of bits in computers :) At least 0xce is documented in SDM.
> >It cannot be implemented in a migration safe manner.
> What do you suggest just say memtest does not work?
Why do you want to run it in a guest?
> I am wondering why it is working with -cpu qemu64.
>
Because memtest has different code for different cpu models.
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 12:42 ` [Qemu-devel] " Gleb Natapov
@ 2012-09-13 12:56 ` Peter Lieven
-1 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 12:56 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On 13.09.2012 14:42, Gleb Natapov wrote:
> On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
>> On 13.09.2012 10:05, Gleb Natapov wrote:
>>> On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
>>>> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>>>>>>>> #rdmsr -0 0x194
>>>>>>>>> 0000000000011100
>>>>>>>>> #rdmsr -0 0xce
>>>>>>>>> 00000c0004011103
>>>>>>> Yes, that can help implementing it in KVM. But without a spec to
>>>>>>> understand what the bits actually mean, it's just as risky...
>>>>>>>
>>>>>>> Peter, do you have any idea where to get the spec of the memory
>>>>>>> controller MSRs in Nehalem and newer processors? Apparently, memtest is
>>>>>>> using them (and in particular 0x194) to find the speed of the FSB, or
>>>>>>> something like that.
>>>>>>>
>>>>> Why would anyone will want to run memtest in a vm? May be just add those
>>>>> MSRs to ignore list and that's it.
>>>> >From the output it looks like it's basically a list of bits. Returning
>>>> something sensible is better, same as for the speed scaling MSRs.
>>>>
>>> Everything is list of bits in computers :) At least 0xce is documented in SDM.
>>> It cannot be implemented in a migration safe manner.
>> What do you suggest just say memtest does not work?
> Why do you want to run it in a guest?
Testing memory thorughput of different host memory layouts/settings
(hugepages, ksm etc.).
Stress testing new settings and qemu-kvm builds.
Testing new nodes with a VM which claims all available pages. Its a lot
easier than booting
a node with a CD and attaching to the Console.
This, of course, is all not missing critical and call also be done with
cpu model qemu64. I just
came across memtest no longer working and where wondering if there is a
general regressing.
BTW, from
http://opensource.apple.com/source/xnu/xnu-1228.15.4/osfmk/i386/tsc.c?txt
#define MSR_FLEX_RATIO 0x194
#define MSR_PLATFORM_INFO 0x0ce
#define BASE_NHM_CLOCK_SOURCE 133333333ULL
#define CPUID_MODEL_NEHALEM 26
switch (cpuid_info()->cpuid_model) {
case CPUID_MODEL_NEHALEM: {
uint64_t cpu_mhz;
uint64_t msr_flex_ratio;
uint64_t msr_platform_info;
/* See if FLEX_RATIO is being used */
msr_flex_ratio = rdmsr64(MSR_FLEX_RATIO);
msr_platform_info = rdmsr64(MSR_PLATFORM_INFO);
flex_ratio_min = (uint32_t)bitfield(msr_platform_info, 47, 40);
flex_ratio_max = (uint32_t)bitfield(msr_platform_info, 15, 8);
/* No BIOS-programed flex ratio. Use hardware max as default */
tscGranularity = flex_ratio_max;
if (msr_flex_ratio & bit(16)) {
/* Flex Enabled: Use this MSR if less than max */
flex_ratio = (uint32_t)bitfield(msr_flex_ratio, 15, 8);
if (flex_ratio < flex_ratio_max)
tscGranularity = flex_ratio;
}
/* If EFI isn't configured correctly, use a constant
* value. See 6036811.
*/
if (busFreq == 0)
busFreq = BASE_NHM_CLOCK_SOURCE;
cpu_mhz = tscGranularity * BASE_NHM_CLOCK_SOURCE;
kprintf("[NHM] Maximum Non-Turbo Ratio = [%d]\n",
(uint32_t)tscGranularity);
kprintf("[NHM] CPU: Frequency = %6d.%04dMhz\n",
(uint32_t)(cpu_mhz / Mega), (uint32_t)(cpu_mhz % Mega));
break;
}
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 12:56 ` Peter Lieven
0 siblings, 0 replies; 42+ messages in thread
From: Peter Lieven @ 2012-09-13 12:56 UTC (permalink / raw)
To: Gleb Natapov; +Cc: Paolo Bonzini, H. Peter Anvin, Avi Kivity, kvm, qemu-devel
On 13.09.2012 14:42, Gleb Natapov wrote:
> On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
>> On 13.09.2012 10:05, Gleb Natapov wrote:
>>> On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
>>>> Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>>>>>>>> #rdmsr -0 0x194
>>>>>>>>> 0000000000011100
>>>>>>>>> #rdmsr -0 0xce
>>>>>>>>> 00000c0004011103
>>>>>>> Yes, that can help implementing it in KVM. But without a spec to
>>>>>>> understand what the bits actually mean, it's just as risky...
>>>>>>>
>>>>>>> Peter, do you have any idea where to get the spec of the memory
>>>>>>> controller MSRs in Nehalem and newer processors? Apparently, memtest is
>>>>>>> using them (and in particular 0x194) to find the speed of the FSB, or
>>>>>>> something like that.
>>>>>>>
>>>>> Why would anyone will want to run memtest in a vm? May be just add those
>>>>> MSRs to ignore list and that's it.
>>>> >From the output it looks like it's basically a list of bits. Returning
>>>> something sensible is better, same as for the speed scaling MSRs.
>>>>
>>> Everything is list of bits in computers :) At least 0xce is documented in SDM.
>>> It cannot be implemented in a migration safe manner.
>> What do you suggest just say memtest does not work?
> Why do you want to run it in a guest?
Testing memory thorughput of different host memory layouts/settings
(hugepages, ksm etc.).
Stress testing new settings and qemu-kvm builds.
Testing new nodes with a VM which claims all available pages. Its a lot
easier than booting
a node with a CD and attaching to the Console.
This, of course, is all not missing critical and call also be done with
cpu model qemu64. I just
came across memtest no longer working and where wondering if there is a
general regressing.
BTW, from
http://opensource.apple.com/source/xnu/xnu-1228.15.4/osfmk/i386/tsc.c?txt
#define MSR_FLEX_RATIO 0x194
#define MSR_PLATFORM_INFO 0x0ce
#define BASE_NHM_CLOCK_SOURCE 133333333ULL
#define CPUID_MODEL_NEHALEM 26
switch (cpuid_info()->cpuid_model) {
case CPUID_MODEL_NEHALEM: {
uint64_t cpu_mhz;
uint64_t msr_flex_ratio;
uint64_t msr_platform_info;
/* See if FLEX_RATIO is being used */
msr_flex_ratio = rdmsr64(MSR_FLEX_RATIO);
msr_platform_info = rdmsr64(MSR_PLATFORM_INFO);
flex_ratio_min = (uint32_t)bitfield(msr_platform_info, 47, 40);
flex_ratio_max = (uint32_t)bitfield(msr_platform_info, 15, 8);
/* No BIOS-programed flex ratio. Use hardware max as default */
tscGranularity = flex_ratio_max;
if (msr_flex_ratio & bit(16)) {
/* Flex Enabled: Use this MSR if less than max */
flex_ratio = (uint32_t)bitfield(msr_flex_ratio, 15, 8);
if (flex_ratio < flex_ratio_max)
tscGranularity = flex_ratio;
}
/* If EFI isn't configured correctly, use a constant
* value. See 6036811.
*/
if (busFreq == 0)
busFreq = BASE_NHM_CLOCK_SOURCE;
cpu_mhz = tscGranularity * BASE_NHM_CLOCK_SOURCE;
kprintf("[NHM] Maximum Non-Turbo Ratio = [%d]\n",
(uint32_t)tscGranularity);
kprintf("[NHM] CPU: Frequency = %6d.%04dMhz\n",
(uint32_t)(cpu_mhz / Mega), (uint32_t)(cpu_mhz % Mega));
break;
}
Peter
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: memtest 4.20+ does not work with -cpu host
2012-09-13 12:56 ` [Qemu-devel] " Peter Lieven
@ 2012-09-13 13:43 ` Gleb Natapov
-1 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 13:43 UTC (permalink / raw)
To: Peter Lieven; +Cc: Paolo Bonzini, Avi Kivity, qemu-devel, kvm, H. Peter Anvin
On Thu, Sep 13, 2012 at 02:56:33PM +0200, Peter Lieven wrote:
> On 13.09.2012 14:42, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> >>On 13.09.2012 10:05, Gleb Natapov wrote:
> >>>On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> >>>>Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>>>>>>>>#rdmsr -0 0x194
> >>>>>>>>>0000000000011100
> >>>>>>>>>#rdmsr -0 0xce
> >>>>>>>>>00000c0004011103
> >>>>>>>Yes, that can help implementing it in KVM. But without a spec to
> >>>>>>>understand what the bits actually mean, it's just as risky...
> >>>>>>>
> >>>>>>>Peter, do you have any idea where to get the spec of the memory
> >>>>>>>controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >>>>>>>using them (and in particular 0x194) to find the speed of the FSB, or
> >>>>>>>something like that.
> >>>>>>>
> >>>>>Why would anyone will want to run memtest in a vm? May be just add those
> >>>>>MSRs to ignore list and that's it.
> >>>>>From the output it looks like it's basically a list of bits. Returning
> >>>>something sensible is better, same as for the speed scaling MSRs.
> >>>>
> >>>Everything is list of bits in computers :) At least 0xce is documented in SDM.
> >>>It cannot be implemented in a migration safe manner.
> >>What do you suggest just say memtest does not work?
> >Why do you want to run it in a guest?
> Testing memory thorughput of different host memory layouts/settings
> (hugepages, ksm etc.).
In may days memtets looked for memory errors. This does not make much
sense in virtualized environment. What does it do today? Calculates
throughput? Does it prefaults memory before doing so, because otherwise
numbers will not be very meaningful when running inside VM. But since
memtets works on physical memory I doubt it prefaults.
> Stress testing new settings and qemu-kvm builds.
Why guest accessing memory stress qemu-kvm?
> Testing new nodes with a VM which claims all available pages. Its a
> lot easier than booting
> a node with a CD and attaching to the Console.
Boot Window, it access all memory :) or run with qemu64 like you say
below.
>
> This, of course, is all not missing critical and call also be done
> with cpu model qemu64. I just
> came across memtest no longer working and where wondering if there
> is a general regressing.
>
If it is a regression it is likely in memtest
> BTW, from http://opensource.apple.com/source/xnu/xnu-1228.15.4/osfmk/i386/tsc.c?txt
>
You can send them patch to check that it runs in a VM and skip all that.
> #define MSR_FLEX_RATIO 0x194
> #define MSR_PLATFORM_INFO 0x0ce
> #define BASE_NHM_CLOCK_SOURCE 133333333ULL
> #define CPUID_MODEL_NEHALEM 26
>
> switch (cpuid_info()->cpuid_model) {
> case CPUID_MODEL_NEHALEM: {
> uint64_t cpu_mhz;
> uint64_t msr_flex_ratio;
> uint64_t msr_platform_info;
>
> /* See if FLEX_RATIO is being used */
> msr_flex_ratio = rdmsr64(MSR_FLEX_RATIO);
> msr_platform_info = rdmsr64(MSR_PLATFORM_INFO);
> flex_ratio_min = (uint32_t)bitfield(msr_platform_info, 47, 40);
> flex_ratio_max = (uint32_t)bitfield(msr_platform_info, 15, 8);
> /* No BIOS-programed flex ratio. Use hardware max as default */
> tscGranularity = flex_ratio_max;
> if (msr_flex_ratio & bit(16)) {
> /* Flex Enabled: Use this MSR if less than max */
> flex_ratio = (uint32_t)bitfield(msr_flex_ratio, 15, 8);
> if (flex_ratio < flex_ratio_max)
> tscGranularity = flex_ratio;
> }
>
> /* If EFI isn't configured correctly, use a constant
> * value. See 6036811.
> */
> if (busFreq == 0)
> busFreq = BASE_NHM_CLOCK_SOURCE;
>
> cpu_mhz = tscGranularity * BASE_NHM_CLOCK_SOURCE;
>
> kprintf("[NHM] Maximum Non-Turbo Ratio = [%d]\n",
> (uint32_t)tscGranularity);
> kprintf("[NHM] CPU: Frequency = %6d.%04dMhz\n",
> (uint32_t)(cpu_mhz / Mega), (uint32_t)(cpu_mhz % Mega));
> break;
> }
>
>
>
> Peter
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
@ 2012-09-13 13:43 ` Gleb Natapov
0 siblings, 0 replies; 42+ messages in thread
From: Gleb Natapov @ 2012-09-13 13:43 UTC (permalink / raw)
To: Peter Lieven; +Cc: Paolo Bonzini, H. Peter Anvin, Avi Kivity, kvm, qemu-devel
On Thu, Sep 13, 2012 at 02:56:33PM +0200, Peter Lieven wrote:
> On 13.09.2012 14:42, Gleb Natapov wrote:
> >On Thu, Sep 13, 2012 at 02:05:23PM +0200, Peter Lieven wrote:
> >>On 13.09.2012 10:05, Gleb Natapov wrote:
> >>>On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> >>>>Il 13/09/2012 09:57, Gleb Natapov ha scritto:
> >>>>>>>>>#rdmsr -0 0x194
> >>>>>>>>>0000000000011100
> >>>>>>>>>#rdmsr -0 0xce
> >>>>>>>>>00000c0004011103
> >>>>>>>Yes, that can help implementing it in KVM. But without a spec to
> >>>>>>>understand what the bits actually mean, it's just as risky...
> >>>>>>>
> >>>>>>>Peter, do you have any idea where to get the spec of the memory
> >>>>>>>controller MSRs in Nehalem and newer processors? Apparently, memtest is
> >>>>>>>using them (and in particular 0x194) to find the speed of the FSB, or
> >>>>>>>something like that.
> >>>>>>>
> >>>>>Why would anyone will want to run memtest in a vm? May be just add those
> >>>>>MSRs to ignore list and that's it.
> >>>>>From the output it looks like it's basically a list of bits. Returning
> >>>>something sensible is better, same as for the speed scaling MSRs.
> >>>>
> >>>Everything is list of bits in computers :) At least 0xce is documented in SDM.
> >>>It cannot be implemented in a migration safe manner.
> >>What do you suggest just say memtest does not work?
> >Why do you want to run it in a guest?
> Testing memory thorughput of different host memory layouts/settings
> (hugepages, ksm etc.).
In may days memtets looked for memory errors. This does not make much
sense in virtualized environment. What does it do today? Calculates
throughput? Does it prefaults memory before doing so, because otherwise
numbers will not be very meaningful when running inside VM. But since
memtets works on physical memory I doubt it prefaults.
> Stress testing new settings and qemu-kvm builds.
Why guest accessing memory stress qemu-kvm?
> Testing new nodes with a VM which claims all available pages. Its a
> lot easier than booting
> a node with a CD and attaching to the Console.
Boot Window, it access all memory :) or run with qemu64 like you say
below.
>
> This, of course, is all not missing critical and call also be done
> with cpu model qemu64. I just
> came across memtest no longer working and where wondering if there
> is a general regressing.
>
If it is a regression it is likely in memtest
> BTW, from http://opensource.apple.com/source/xnu/xnu-1228.15.4/osfmk/i386/tsc.c?txt
>
You can send them patch to check that it runs in a VM and skip all that.
> #define MSR_FLEX_RATIO 0x194
> #define MSR_PLATFORM_INFO 0x0ce
> #define BASE_NHM_CLOCK_SOURCE 133333333ULL
> #define CPUID_MODEL_NEHALEM 26
>
> switch (cpuid_info()->cpuid_model) {
> case CPUID_MODEL_NEHALEM: {
> uint64_t cpu_mhz;
> uint64_t msr_flex_ratio;
> uint64_t msr_platform_info;
>
> /* See if FLEX_RATIO is being used */
> msr_flex_ratio = rdmsr64(MSR_FLEX_RATIO);
> msr_platform_info = rdmsr64(MSR_PLATFORM_INFO);
> flex_ratio_min = (uint32_t)bitfield(msr_platform_info, 47, 40);
> flex_ratio_max = (uint32_t)bitfield(msr_platform_info, 15, 8);
> /* No BIOS-programed flex ratio. Use hardware max as default */
> tscGranularity = flex_ratio_max;
> if (msr_flex_ratio & bit(16)) {
> /* Flex Enabled: Use this MSR if less than max */
> flex_ratio = (uint32_t)bitfield(msr_flex_ratio, 15, 8);
> if (flex_ratio < flex_ratio_max)
> tscGranularity = flex_ratio;
> }
>
> /* If EFI isn't configured correctly, use a constant
> * value. See 6036811.
> */
> if (busFreq == 0)
> busFreq = BASE_NHM_CLOCK_SOURCE;
>
> cpu_mhz = tscGranularity * BASE_NHM_CLOCK_SOURCE;
>
> kprintf("[NHM] Maximum Non-Turbo Ratio = [%d]\n",
> (uint32_t)tscGranularity);
> kprintf("[NHM] CPU: Frequency = %6d.%04dMhz\n",
> (uint32_t)(cpu_mhz / Mega), (uint32_t)(cpu_mhz % Mega));
> break;
> }
>
>
>
> Peter
--
Gleb.
^ permalink raw reply [flat|nested] 42+ messages in thread
end of thread, other threads:[~2012-09-13 13:43 UTC | newest]
Thread overview: 42+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-22 15:06 memtest 4.20+ does not work with -cpu host Peter Lieven
2012-08-22 15:06 ` [Qemu-devel] " Peter Lieven
2012-09-06 14:58 ` Avi Kivity
2012-09-06 14:58 ` [Qemu-devel] " Avi Kivity
2012-09-10 11:06 ` Peter Lieven
2012-09-10 11:06 ` [Qemu-devel] " Peter Lieven
2012-09-10 11:29 ` Paolo Bonzini
2012-09-10 11:29 ` [Qemu-devel] " Paolo Bonzini
2012-09-10 11:47 ` Peter Lieven
2012-09-10 11:47 ` [Qemu-devel] " Peter Lieven
2012-09-10 11:52 ` Peter Lieven
2012-09-10 11:52 ` [Qemu-devel] " Peter Lieven
2012-09-10 12:15 ` Paolo Bonzini
2012-09-10 12:15 ` [Qemu-devel] " Paolo Bonzini
2012-09-10 12:21 ` Gleb Natapov
2012-09-10 12:21 ` [Qemu-devel] " Gleb Natapov
2012-09-10 12:29 ` Peter Lieven
2012-09-10 12:29 ` [Qemu-devel] " Peter Lieven
2012-09-10 12:32 ` Avi Kivity
2012-09-10 12:32 ` [Qemu-devel] " Avi Kivity
2012-09-10 12:38 ` Peter Lieven
2012-09-10 12:38 ` [Qemu-devel] " Peter Lieven
2012-09-13 7:53 ` Peter Lieven
2012-09-13 7:53 ` [Qemu-devel] " Peter Lieven
2012-09-13 7:55 ` Paolo Bonzini
2012-09-13 7:55 ` [Qemu-devel] " Paolo Bonzini
2012-09-13 7:57 ` Gleb Natapov
2012-09-13 7:57 ` [Qemu-devel] " Gleb Natapov
2012-09-13 8:00 ` Paolo Bonzini
2012-09-13 8:00 ` [Qemu-devel] " Paolo Bonzini
2012-09-13 8:05 ` Gleb Natapov
2012-09-13 8:05 ` [Qemu-devel] " Gleb Natapov
2012-09-13 12:05 ` Peter Lieven
2012-09-13 12:05 ` [Qemu-devel] " Peter Lieven
2012-09-13 12:42 ` Gleb Natapov
2012-09-13 12:42 ` [Qemu-devel] " Gleb Natapov
2012-09-13 12:56 ` Peter Lieven
2012-09-13 12:56 ` [Qemu-devel] " Peter Lieven
2012-09-13 13:43 ` Gleb Natapov
2012-09-13 13:43 ` [Qemu-devel] " Gleb Natapov
2012-09-10 12:12 ` Avi Kivity
2012-09-10 12:12 ` [Qemu-devel] " Avi Kivity
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.