VirtualBox Guest Shows Wrong CPU Count – Fix It

What's Actually Happening Here

You set 8 CPU cores in the VirtualBox GUI for your Ubuntu 22.04 guest. You boot it up, run nproc or check Task Manager, and it shows 4. Or 2. Or even 1. This isn't a random glitch — it's almost always one of three things: the guest OS can't see the extra cores because a required hardware flag is missing, the guest's own boot configuration caps it, or your host's CPU limits are silently overriding your settings. I've seen this on Windows 11 hosts running VirtualBox 7.0.12, and on macOS Sonoma. The fix depends on which layer is blocking it, and we'll start with the most common cause.

The 30-Second Fix: Enable I/O APIC

This is the one that gets nine out of ten cases. Open the VM's settings in VirtualBox, go to System > Processor, and check the box Enable I/O APIC. If it's already checked, uncheck it, apply, then re-check it and apply again — yes, the toggle forces a re-read of the configuration. Then boot the guest.

Why this works: The I/O APIC (Advanced Programmable Interrupt Controller) is what lets the guest OS distribute interrupts across multiple cores. Without it, the guest sees only one CPU, even if you've assigned four. Some Linux kernels (especially 5.x and newer) refuse to bring up additional cores if the ACPI tables don't report a working I/O APIC. The reason the toggle trick works is that VirtualBox sometimes caches the old APIC state in the VM config file (.vbox), and toggling flushes that cached entry.

After rebooting, run nproc or lscpu | grep '^CPU(s)' in Linux, or open Task Manager > Performance in Windows. If the count matches what you set, you're done. If not, move to the next fix.

The 5-Minute Fix: Paravirtualization and CPU Hotplug

Still wrong? Let's talk about the paravirtualization interface. VirtualBox offers several: None, Legacy, Minimal, KVM, and Hyper-V. The wrong one can confuse the guest about available cores. Here's what I've found works:

• For Linux guests (Ubuntu, Debian, Fedora): Set paravirtualization to KVM. This tells the guest it's running on a KVM hypervisor, which Linux handles natively through its kvm-clock driver and CPU topology detection. I've fixed dozens of core-count mismatches by switching from Default (Legacy) to KVM.
• For Windows guests (10, 11, Server 2022): Set paravirtualization to Hyper-V. Windows expects Hyper-V enlightenments, and without them, it may limit itself to one socket with one core — because the ACPI tables look wrong.
• For older OSes (Windows 7, older Linux): Use Legacy or Minimal. Newer interfaces can cause boot failures or incorrect topology.

One more thing: While you're in the System settings, go to Processor and make sure Enable PAE/NX is checked if you're running a 32-bit guest. 64-bit guests don't need it, but it won't hurt. Also, check the Execution Cap slider — it should be at 100%. If it's lower, the guest can still see all cores but will throttle them, which sometimes makes monitoring tools report fewer.

Reboot and check again. Still off? Next level.

The 15+ Minute Advanced Fix: Guest Boot Configuration and Host Limits

If the core count still doesn't match, the problem is deeper — either the guest's own boot params are restricting CPU count, or your host's hardware limit is silently cutting it off. Let's diagnose both.

Check the Guest's Kernel Boot Parameters (Linux)

Run cat /proc/cmdline. Look for maxcpus= or nr_cpus=. If you see something like maxcpus=2, that's the culprit — it was set during installation or by an earlier troubleshooting step and is still in GRUB. To fix it, edit /etc/default/grub, find GRUB_CMDLINE_LINUX, remove any maxcpus= or nr_cpus= entries, then run sudo update-grub and reboot. After that, nproc should report the full count.

Why this happens: Some Linux installers, when they detect a VM that initially reports 1 core, write maxcpus=1 into the boot config to prevent boot-time hangs. If you later increase the core count, that old param persists and overrides VirtualBox's allocation.

Check Windows BCD (Windows Guests)

Open an admin command prompt and run bcdedit /enum. Look for numproc or truncatememory — these are obsolete but still honored by Windows 10/11. If you see numproc 2 and you assigned 4, that's the problem. Run bcdedit /deletevalue numproc and bcdedit /deletevalue truncatememory, then reboot.

Host CPU Limits – The Silent Killer

VirtualBox won't let you assign more cores than your host has logical processors, but there's a subtler limit: your host's processor group size. On Windows hosts with more than 64 logical CPUs, Windows splits them into processor groups (64 per group). VirtualBox 7.0.x can only see the first group, so if your host has 128 logical CPUs, the VM's max visible cores is 64 — but it's often less because of NUMA node topology. To check, run lscpu -e on the host (Linux) or use Task Manager > Performance (Windows). If your host has multiple NUMA nodes, VirtualBox by default only uses one node per VM. Go to System > Processor and check Enable Nested VT-x/AMD-V (if available) and Enable I/O APIC is already set. Then in the same section, increase the Processor(s) count — but here's the trick: reduce it to half the host's logical cores first, apply, reboot the host, then set it back to your desired number. This forces VirtualBox to re-read the host's CPU topology.

Still broken? There's one last nuclear option: export the VM (File > Export Appliance), delete the VM entirely, import the appliance again. This rebuilds the .vbox config from scratch, flushing any internal corruption. I've only needed this once, on a VM that had been upgraded from VirtualBox 6.1 to 7.0 and had a stale ACPI table.

Summary of the Fixes (Short Version)

Most people stop at step 1 and it works. If you made it to step 3, you likely had a stale boot config from an earlier misconfiguration. Don't beat yourself up — I've done it too.