Core vs Socket Basics
In KVM virtualization, each vCPU can be exposed as a “core” on a virtual socket. You decide whether to pack all cores into one socket or spread them across multiple sockets, depending on OS and licensing requirements.
| Term | Definition |
|---|---|
| Core | The individual processing unit within a CPU. |
| Socket | The physical (or virtual) CPU package; can host multiple cores. |
| vCPU | A virtual CPU presented to the guest OS—mapped to cores/sockets based on your topology. |
Why the Topology Matters
- Operating system limits – Many Windows editions recognize only two sockets but support dozens of cores per socket. Linux is generally flexible.
- Licensing models – Some software counts sockets (SQL Server Standard, certain hypervisor licenses) while others count cores.
- NUMA-aware workloads – Apps optimized for multi-socket systems may benefit from spreading cores across sockets, while cache-sensitive workloads often prefer a single socket packed with cores.
Change the CPU Topology in the Portal
1
Open CPU settings
In the EDBB VPS Portal, open your VPS and switch to the Settings tab. Locate the CPU Cores vs Sockets control.
2
Pick the layout
Choose whether you want multiple sockets or multiple cores. The portal automatically maps your vCPU allotment to the selected layout.
3
Apply and reboot
Click Apply, then power-cycle or reboot the VPS so the guest OS detects the new topology cleanly.
Tip: Before adjusting topology, confirm your OS and application licensing terms to avoid unintended compliance issues.