Container / VMs nutzen nur einen CPU Kern

[AgentSphynx]

Hallo,
wie im Titel erwähnt nutzt Proxmox leider nur ein CPU Kern.
Wenn ich zb. 4 bei der LXC Erstellung auswähle bleibt die CPU beim Monitoring trotzdem nur bei 25% & einem Kern.
Woran könnte es liegen?


Hier mal ein paar Infos:

proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-helper: 7.1-2 pve-kernel-5.11: 7.0-7 pve-kernel-5.11.22-4-pve: 5.11.22-9 pve-kernel-5.11.22-3-pve: 5.11.22-7 pve-kernel-5.11.22-1-pve: 5.11.22-2 ceph-fuse: 15.2.13-pve1 corosync: 3.1.5-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve1 libproxmox-acme-perl: 1.3.0 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.0-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.0-9 libpve-guest-common-perl: 4.0-2 libpve-http-server-perl: 4.0-2 libpve-storage-perl: 7.0-11 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.9-4 lxcfs: 4.0.8-pve2 novnc-pve: 1.2.0-3 proxmox-backup-client: 2.0.10-1 proxmox-backup-file-restore: 2.0.10-1 proxmox-mini-journalreader: 1.2-1 proxmox-widget-toolkit: 3.3-6 pve-cluster: 7.0-3 pve-container: 4.0-10 pve-docs: 7.0-5 pve-edk2-firmware: 3.20200531-1 pve-firewall: 4.2-3 pve-firmware: 3.3-1 pve-ha-manager: 3.3-1 pve-i18n: 2.5-1 pve-qemu-kvm: 6.0.0-4 pve-xtermjs: 4.12.0-1 qemu-server: 7.0-14 smartmontools: 7.2-1 spiceterm: 3.2-2 vncterm: 1.7-1 zfsutils-linux: 2.0.5-pve1

Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 69 Model name: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz Stepping: 1 CPU MHz: 1696.171 CPU max MHz: 1700.0000 CPU min MHz: 800.0000 BogoMIPS: 3392.00 Virtualization: VT-x L1d cache: 64 KiB L1i cache: 64 KiB L2 cache: 512 KiB L3 cache: 3 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI 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; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Vulnerable: No microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1 gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm a bm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 sm ep bmi2 erms invpcid xsaveopt dtherm arat pln pts md_clear flush_l1d

# dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Intel Corp. Version: WYLPT10H.86A.0054.2019.0902.1752 Release Date: 09/02/2019 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 6656 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Product Name: Version: Serial Number: UUID: srthjsrth-35444-45e1-errz45-catheastha Wake-up Type: Power Switch SKU Number: Family: Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Intel Corporation Product Name: D34010WYK Version: H14771-304 Serial Number: GEXXXXXXXXXX Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x001D, DMI type 10, 10 bytes On Board Device 1 Information Type: Video Status: Enabled Description: Intel(R) HD Graphics Device On Board Device 2 Information Type: Ethernet Status: Enabled Description: Intel(R) WGI218V Gigabit Network Device On Board Device 3 Information Type: Sound Status: Enabled Description: Realtek High Definition Audio Device Handle 0x001F, DMI type 12, 5 bytes System Configuration Options Option 1: To Be Filled By O.E.M. Handle 0x0021, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x0037, DMI type 41, 11 bytes Onboard Device Reference Designation: CPU1 Type: Video Status: Enabled Type Instance: 1 Bus Address: 0000:00:02.0 Handle 0x0038, DMI type 41, 11 bytes Onboard Device Reference Designation: ILAN Type: Ethernet Status: Enabled Type Instance: 1 Bus Address: 0000:00:19.0 Handle 0x0039, DMI type 41, 11 bytes Onboard Device Reference Designation: AUDIO1 Type: Sound Status: Enabled Type Instance: 1 Bus Address: 0000:00:1b.0 Handle 0x003A, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Core i3 Manufacturer: Intel(R) Corp. ID: 51 06 04 00 FF FB EB BF Signature: Type 0, Family 6, Model 69, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz Voltage: 1.2 V External Clock: 100 MHz Max Speed: 1700 MHz Current Speed: 1700 MHz Status: Populated, Enabled Upgrade: Socket LGA1150 L1 Cache Handle: 0x003C L2 Cache Handle: 0x003B L3 Cache Handle: 0x003D Serial Number: Not Specified Asset Tag: Fill By OEM Part Number: Fill By OEM Core Count: 2 Core Enabled: 2 Thread Count: 4 Characteristics: 64-bit capable Handle 0x005D, DMI type 13, 22 bytes BIOS Language Information Language Description Format: Long Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1

Genutzt wird ein Intel NUC. Einen Bios Update hatte ich vor der Installation von Proxmox durchgeführt.

Viele Grüße.

 

[Dunuin]

Ist im BIOS vielleicht die Anzahl der Kerne beschränkt? Ich meine bei mir da mal was gesehen zu haben, dass ich im BIOS sagen konnte, wieviele meine physischen CPU-Kerne ich denn maximal nutzen möchte.

Ansonsten ist auch noch die Frage was genau du im Gast laufen lässt. Wenn ein Gast 4 Kerne bekommen hat aber da nur eine Anwendung läuft, die ausschließlich single-threaded läuft, dann kann die Anwendung halt software gedingt auch nicht mehr als einen Kern nutzen und der LXC/VM wird nur knapp über 25% liegen, da das OS natürlich noch die anderen Kerne nutzen könnte aber ja normal nicht viel zu tun hat.