Virtual SMP in VMware Workstation Player: Configure Multiple Virtual CPUs

Learn how Virtual SMP gives one VMware Workstation Player VM multiple virtual CPUs, check host requirements, configure four vCPUs, and validate performance.

Virtual SMP, or virtual symmetric multiprocessing (vSMP), lets one virtual machine use multiple virtual CPUs at the same time. This can increase the CPU capacity available to a guest operating system and its applications when they support parallel execution.

This is different from running several separate virtual machines. Multiple VMs divide the host's resources among independent guests; vSMP gives several virtual CPUs to one guest so that one operating system and its applications can execute concurrent work.

What Virtual SMP means

Symmetric multiprocessing (SMP) is a computing model in which multiple processors can participate in running operating-system and application work. In a physical computer, the operating system schedules tasks across available processors or cores.

Virtual SMP is the virtualization equivalent: the hypervisor presents multiple virtual CPUs to one virtual machine. A vCPU is a virtual CPU presented by the hypervisor to the guest operating system. The guest schedules work across those vCPUs as if it had access to multiple processors.

The main benefit is greater CPU capacity for a single guest. For example, a database server handling concurrent queries or background jobs may use several vCPUs simultaneously. A mostly single-threaded application, however, may gain little from additional vCPUs because it cannot divide its main workload across multiple execution paths.

Virtual CPUs, processors, and cores

VMware Workstation Player can describe the guest CPU topology using a processor count and a cores-per-processor value. The guest-visible CPU total is calculated as:

total guest-visible vCPUs = virtual processors × cores per processor

The guest operating system detects this configured topology. Thus, a setting of two virtual processors with two cores per processor presents four vCPUs, while one virtual processor with four cores per processor also presents four vCPUs when those settings are available in the application.

Single-vCPU baseline

Virtual processor setting: 1

Cores per processor setting: 1

Total guest-visible vCPUs: 1

Example use: Lightweight desktop work or an application with minimal CPU demand.

Two-vCPU configuration

Virtual processor setting: 1

Cores per processor setting: 2

Total guest-visible vCPUs: 2

Example use: A modest multitasking guest or a workload with some parallel activity.

Four-vCPU configuration

Virtual processor setting: 1 or 2, depending on the available topology controls

Cores per processor setting: 4 when using one processor, or 2 when using two processors

Total guest-visible vCPUs: 4

Example use: A database or other parallel-capable workload that has demonstrated a need for more CPU capacity.

Host requirements

The host system is the physical computer running VMware Workstation Player. Before configuring a multiprocessor guest, the host must expose at least two logical processors.

A logical processor is a CPU execution unit reported by the host operating system. It may correspond to a physical core or to a hardware thread created by simultaneous multithreading (SMT), also commonly called Hyper-Threading. A physical CPU is a processor package installed in the computer, while a CPU core is an independent processing unit inside that package.

Two or more physical CPUs

Why it qualifies: The computer has multiple processor packages that can execute work independently.

Logical-processor implication: The host normally reports at least one or more logical processors for each package, so the total can support a multiprocessor guest.

One physical CPU with multiple cores

Why it qualifies: A single processor package contains at least two independent physical cores.

Logical-processor implication: The host reports the cores as multiple logical processors.

A processor with Hyper-Threading or SMT enabled

Why it qualifies: The processor exposes more than one hardware thread per physical core.

Logical-processor implication: The host can report at least two logical processors even when the number of physical cores is lower than the logical-processor count.

Host CPU availability sets a practical limit on useful guest allocation. Logical processors exposed through SMT can improve concurrency, but they are not equivalent to adding the same number of additional physical cores. Leave enough processing capacity for the host operating system and for other applications or VMs running at the same time.

When Virtual SMP is appropriate

Database servers: Concurrent queries, transaction processing, indexing, and background tasks may run in parallel.
Customer relationship management systems: Application services, reporting, scheduled jobs, and user requests may benefit from several execution paths.
Other parallel workloads: Software that is designed to use multiple threads can make better use of additional vCPUs.

Adding vCPUs is beneficial only when all three layers can use them: the guest operating system must support the assigned CPU topology, the application must be capable of parallel execution, and the workload must have enough concurrent work. A low-parallelism application may perform nearly the same with one vCPU.

Configure Virtual SMP for an existing VM

Power off the virtual machine before changing its virtual hardware. Suspending the VM or leaving it running may prevent the processor configuration from being changed safely.

Select the target virtual machine in the VMware Workstation Player library.
Open Player > Manage > Virtual Machine Settings.
Open the Hardware tab.
Select Processors in the hardware list.
Set the processor and cores-per-processor values needed for the workload. For the primary example, configure a total of four virtual CPU cores. For example, use one processor with four cores per processor, or another four-vCPU arrangement offered by the interface.
Select OK to save the setting.
Start the virtual machine and verify the processor count from inside the guest operating system.

The exact labels or available topology combinations can vary with the VMware Workstation Player version, VM compatibility level, host platform, and guest configuration. Always confirm the resulting total using the multiplication rule rather than relying on only one field.

Plan vCPU capacity carefully

Size vCPUs according to measured workload demand, not according to the maximum value the interface permits. More vCPUs do not automatically mean better performance.

CPU contention occurs when the host operating system and running VMs compete for limited host execution capacity.
Assigning too many vCPUs can make the host less responsive and can increase scheduling overhead for the VM.
A guest with many idle vCPUs still consumes scheduling capacity and may compete with other workloads.
Leave sufficient CPU resources for the host operating system, monitoring tools, and applications running concurrently.
Increase the allocation incrementally, then measure whether the workload improves.

For example, a four-vCPU database VM may be appropriate on a host with several logical processors if monitoring shows concurrent database work. The same allocation may be excessive on a lightly equipped host running several other VMs.

Verify the configuration and its effect

Start or restart the guest after saving the virtual hardware change.
Open the guest operating system's system-information page or task/performance monitor.
Confirm that the expected number of logical processors is visible. A four-vCPU configuration should normally appear as four guest-visible logical processors, subject to guest operating-system limits and topology handling.
Run the intended workload and observe CPU utilization in the guest.
Observe the host's performance monitor as well, checking for CPU contention and whether other VMs or host applications are consuming the available capacity.

Successful CPU detection is not the same as a performance improvement. If the guest reports four processors but the application remains limited to one execution thread, its performance may not change. Check whether the bottleneck is CPU, memory, storage, networking, or an external service before assigning more vCPUs.

Troubleshooting Virtual SMP

The VM cannot be configured with multiple virtual CPUs

Check whether the host operating system reports at least two logical processors.
Confirm that the host CPU's multiple cores or hardware-threading feature is available and enabled where applicable.
Ensure the VM is powered off before editing its virtual hardware.
Review the VM's compatibility level and guest configuration if the processor controls are restricted.

The guest sees fewer CPUs than expected

Reopen Player > Manage > Virtual Machine Settings > Hardware > Processors and confirm the processor and core values.
Confirm that the setting was saved with OK.
Restart the guest after changing virtual hardware.
Check whether the guest operating-system edition or configuration supports the assigned CPU topology.

Adding vCPUs does not improve performance

Measure CPU utilization in both the guest and the host.
Determine whether the application is mostly single-threaded.
Check for memory, storage, network, or external-service bottlenecks.
Reduce unnecessary vCPU allocation if the workload does not use it, or free host capacity by stopping competing workloads.

The host becomes slow after increasing the VM CPU allocation

The VM may have too many vCPUs relative to the host's logical processors.
Other VMs or host applications may be consuming CPU at the same time.
Lower the VM's vCPU count to match demonstrated demand and reserve adequate processing capacity for the host.

Key points

Virtual SMP presents multiple vCPUs to one guest VM; it is not the same as running multiple separate VMs.
The guest-visible total is the virtual processor count multiplied by cores per processor.
The host must expose at least two logical processors for a multiprocessor guest configuration.
Four vCPUs can be configured through the Processors hardware category using an available processor/core topology.
Parallel-capable applications benefit most, while single-threaded workloads may not improve.
Measure both guest performance and host contention before and after changing the allocation.

For related virtual hardware tasks, see changing memory allocation, configuring VM compatibility, and the VMware Workstation Player course.