Silly Proxmox CPU detection question

[Stokkes]

Hey all

 

This is just a silly question (not sure if it has any real impacts) - No problems running Unraid on Proxmox, ESXi, etc for a few years.

 

The CPU "type" in Proxomox for the Unraid VM is set to "Host", however, the Unraid dashboard detects the CPU as "pc-q35-6.0" at 2000Mhz,

 

But the funny thing is, running lscpu in the Unraid terminal detects the right CPU:

 

Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           165
Model name:                      Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz
Stepping:                        5
CPU MHz:                         2807.986
BogoMIPS:                        5615.97
Virtualization:                  VT-x
Hypervisor vendor:               KVM
Virtualization type:             full
L1d cache:                       256 KiB
L1i cache:                       256 KiB
L2 cache:                        32 MiB
L3 cache:                        16 MiB
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfl
                                 ush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_p
                                 erfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 
                                 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
                                 xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpc
                                 id_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ep
                                 t vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdsee
                                 d adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves arat umip pku ospke md_
                                 clear arch_capabilities

 

Curious if anyone has any ideas.. Just a bit of OCD going on

 

[jevis]

Having the same OCD here 😄, did you figure out the cause of the wrong Dashboard info?

[Stokkes]

I did not unfortunately. 

[SimonF]

7 hours ago, Stokkes said:

I did not unfortunately. 

What does this output?

 

grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo

[Stokkes]

6 hours ago, SimonF said:

What does this output?

 

grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo

 

❯ grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo                                                  Wed 25 May 08:45:03 
Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz

 

[SimonF]

4 hours ago, Stokkes said:

 

❯ grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo                                                  Wed 25 May 08:45:03 
Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz

 

Thanks which os vers are you using also can you provide a screen print of the affected panel?

[Stokkes]

2 minutes ago, SimonF said:

Thanks which os vers are you using also can you provide a screen print of the affected panel?

Latest, 6.10.1

 

Attached a screenshot of the panel in the Dashboard that shows the Proxmox pc-q35 cpu.. Like I mentioned above, it's not a big deal, just OCD and weird it doesn't detect the right CPU.

 

 

 

 

[SimonF]

51 minutes ago, Stokkes said:

Latest, 6.10.1

 

Attached a screenshot of the panel in the Dashboard that shows the Proxmox pc-q35 cpu.. Like I mentioned above, it's not a big deal, just OCD and weird it doesn't detect the right CPU.

 

 

 

 

 

Sorry the code I sent before is called if this is doesn't exists if version doesnt exist in dmidecode

 

does this have pc-q35...... dmidecode | grep Version

Edited May 25, 2022 by SimonF

[Stokkes]

Here's the output

 

❯ sudo dmidecode | grep Version                                                                     Wed 25 May 14:03:10 
	Version: pc-q35-6.0
	Version: pc-q35-6.0
	Version: pc-q35-6.0
	Version: 0.0.0

 

[limawaken]

my unraid dashboard displays the CPU as "pc-q35-7.1 at 2000Mhz"

i'm also wondering if this can be fixed?

i'm on 6.11.5

[SimonF]

Not sure if this will work or will break things, but you may be able to set the BIOS for the VM in proxmox to be host values.

 

<os>

<type arch="x86_64">hvm</type>

<smbios mode="host"/>

</os>

[limawaken]

sorry, i'm a proxmox noob...

where do i set the bios?

[neruve]

Not to revive this, but has there been any fixes for this? I am having the same issue.