Bug 808806 - host dmesg shows warnning "kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround"
host dmesg shows warnning "kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not w...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.3
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-01 02:30 EDT by Xiaoqing Wei
Modified: 2012-04-01 03:07 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-01 03:07:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Xiaoqing Wei 2012-04-01 02:30:22 EDT
Description of problem:

host dmesg shows warnning "kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround"

Version-Release number of selected component (if applicable):

2.6.32-251.el6.x86_64

How reproducible:
2 / 2

Steps to Reproduce:
1.install a rhel6 with kernel 2.6.32-251.el6.x86_64
2.# dmesg | grep -i kvm
kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
kvm: already loaded the other module
3.
  
Actual results:
host dmesg shows warnning "kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround"

for now, it didn't harm my tests. but no knowing if it will,
 if this warnning is expected. pls close this bug.
Expected results:
not warning or ?

Additional info:

..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Xeon(R) CPU           E5530  @ 2.40GHz stepping 05
Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
Booting Node   0, Processors  #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15
Brought up 16 CPUs
Total of 16 processors activated (76596.03 BogoMIPS).
Comment 3 Suqin Huang 2012-04-01 02:42:20 EDT
Hi gleb,
Can you have a look this bug.

Thanks
Suqin
Comment 4 Gleb Natapov 2012-04-01 03:07:42 EDT
This message it OK. It means host CPU has an erratum and code works around it.

Note You need to log in before you can comment on or make changes to this bug.