Cisco Unity Connection

UCS - Host Fails to Boot after the OVA Template Loads

Document ID: 117689

Updated: May 27, 2014

Contributed by Scott Hills, Cisco TAC Engineer.



This document describes a problem encountered on a Unified Computing System (UCS) platform with an E7 processor where the Open Virtualization Archive (OVA) template loads but the host does not boot.


Systems that run a UCS platform with an E7 processor sometimes experience a problem where the host fails to boot after the OVA template loads. This failure produces this error message:

    An error was received from the ESX host while powering on VM VaderServer1.
Failed to power on VM.
Could not power on VM : CPU min outside valid range.
Group host/user: Invalid CPU allocation requested for VM vmm0:VaderServer1.
(min: 5060 mhz, max: -1, minLimit: -1, shares: -3)


In Release 8.6(2) and later, Central Processor Unit (CPU) reservations are contained in the OVA. CPU reservation numbers are based on the Xeon 7500 processor which, when run on the E7 processor, are higher than the cycles available on a virtual CPU. Lab tests have determined that the 2.4 GHz E7 processor has the same performance as a 2.53 GHz Xeon 7500 processor; therefore, you can manually change the reservation numbers for 5,000, 10,000, or 20,000 deployment options on a virtual machine that runs on an E7 processor.

  1. In the VMware vSphere Client, select the host on which the virtual machine was created.
  2. Click the Summary tab under CPU chore. Note the available CPU cycles, in GHz, for one virtual CPU.
  3. Power off the virtual machine on which you deployed the OVA template.
  4. In the left pane of the  vSphere Client, right-click the name of the virtual machine and select Edit Settings.
  5. In the Virtual Machine Properties dialog box, select the Resources tab.
  6. In the Settings column, select CPU.
  7. Under Resource Allocation, in the Reservation text box, enter the new reservation value (the number of CPUs multiplied by the available CPU cycles, in GHz, for one virtual CPU as determined in step 2).
  8. Click OK to close the Virtual Machine Properties dialog box.
  9. Power on the virtual machine.

Related Information

Updated: May 27, 2014
Document ID: 117689