Failing CPU detection

  • 83 Views
  • Last Post 5 weeks ago
  • Topic Is Solved
Veltys posted this 22 July 2019

Hello everyone!

I've installed and configured AMP in a Debian 9.9 VPS from Contabo.

After installing, I can see AMP can't detect correctly my CPU:

Debian GNU/Linux 9 (stretch) | 16051MB RAM 
0x Unknown CPU Model(0C/0T)

If I execute cat /proc/cpuinfo, it gives six times (six-core CPU) this information:

processor       : [core number 0 to 5]
vendor_id       : GenuineIntel
cpu family      : 6
model           : 79
model name      : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
stepping        : 1
microcode       : 0x1
cpu MHz         : 2199.998
cache size      : 16384 KB
physical id     : 0
siblings        : 6
core id         : 0
cpu cores       : 6
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb kaiser fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt arat
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 4399.99
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

I hope this information would help to improve the CPU detection and AMP could detect correctly my CPU.

🤔 By the way... maybe I need something (like a package) to enable this detection? For example, this machines doesn't come with some 'basic' (at least for me) packages like sudo or man. Is it possible I need another additional package? I previously tested AMP on AWS EC2 machines and CPU detection works fine.

Thanks!

Order By: Standard | Newest | Votes
Mike posted this 22 July 2019

There's a known issue where AMP couldn't detect the CPU model in OpenVZ VPSs specifically. It was caused by 'lscpu' also failing to do the same. The issue has been fixed already in the Nightly build.

Veltys posted this 22 July 2019

First of all, thank you for your very quick answer.

Regarding my VPS virtualization technology... I'm not sure. I know they use 'QEMU' and 'KVM', but I didn't find anything talking about OpenVZ. virt-what app tells me 'kvm' and dmidecode tells 'QEMU'. Sorry for not being very helpful.

On the other hand, lscpu command also works fine:

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                6
On-line CPU(s) list:   0-5
Thread(s) per core:    1
Core(s) per socket:    6
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
Stepping:              1
CPU MHz:               2199.998
BogoMIPS:              4399.99
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              4096K
L3 cache:              16384K
NUMA node0 CPU(s):     0-5
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb kaiser fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt arat

Should I wait next version?

Thanks one more time for your help!

Mike posted this 22 July 2019

AMPs own log will tell you what virtualizer is running too. Does lscpu work fine as the AMP user specifically?

Veltys posted this 24 July 2019

AMPs own log will tell you what virtualizer is running too.

[19:37:30] [Core Info]            : Starting AMP version 1.8.2.2 (TITAN), built 05/07/2019 11:38
[19:37:30] [Core Info]            : Release spec: Release - built by CUBECODERS/BuildBot on CCL-DEV
[19:37:30] [Core Info]            : Running in a QEMU KVM environment.
[19:37:30] [Core Warning]         : Current time zone is set to CET - Servers should ideally be UTC to avoid time-zone related issues
[19:37:30] [Core Info]            : OS: Linux / x86_64
[19:37:30] [Core Info]            : CPU: Unknown CPU Model (0C/0T)

Does lscpu work fine as the AMP user specifically?

Yes, it does:

AMP@Iuppiter:~$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                6
On-line CPU(s) list:   0-5
Thread(s) per core:    1
Core(s) per socket:    6
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
Stepping:              1
CPU MHz:               2199.998
BogoMIPS:              4399.99
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              4096K
L3 cache:              16384K
NUMA node0 CPU(s):     0-5
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb kaiser fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt arat

Mike posted this 24 July 2019

Interesting, I'll look into it.

Veltys posted this 5 weeks ago

Release 1.8.3.0 fixed everything. Thank you so much!! 😄

Close