Skip to main content
nsamuel
Staff
Staff
January 7, 2016

Meru Technical Note - VM failed to power on. Could not power on VM.

  • January 7, 2016
  • 0 replies
  • 709 views
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"


Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.