Wireless Controller
Dedicated Wi-Fi control and management for high density and mobility
nsamuel
Staff
Staff
Article Id 194547
Description

VM failed to power on. Could not power on VM.

The possibilities are: 

  • Number of running VCPUs limit might have exceeded. 
  • The number of virtual CPUs (4) is greater than the number of physical CPUs (2).
  • If  virtual machine's host does not have enough memory for the reservation required.
  • If  virtual machine's resource usage does not match its resource settings.

Scope

KB Article Type: Configuration

RELATED PRODUCTS: Virtual Controller and Ezrf

RELATED SOFTWARE VERSIONS: 5.3-132v, 3.2-39v

KEYWORDS: vm


Solution

To reduce the CPU virtual socket from 4 to 2 :

Right click from Virtual Machine > Edit settings>CPUs> Change virtual socket from 4 to 2.

Edit the vmx file before updating in the data store

Change: numvcpus = "2", maxvcpus = "2"


Contributors