upgrading from v8.1 to v10.2 but after OVA deployment cannot start VM - Errors Failed to power on virtual machine CM v 10.2

Doc ID    SOLN386588
Version:    1.0
Status:    Published
Published date:    28 May 2026
Author:   
svsalve
 

Details

upgrading from v8.1 to v10.2 but after OVA deployment cannot start VM - Errors Failed to power on virtual machine CM v 10.2

Problem Clarification

upgrading from v8.1 to v10.2 but after OVA deployment cannot start VM - Errors Failed to power on virtual machine CM v 10.2
 

Cause

In the Investigation, it was idnetified that you are using Intel Xeon Silver 4514Y processors (which have a base clock speed of 2.0 GHz), the system is technically running below Avaya’s "standard" requirements for high-capacity footprints.[1]

 

Solution

For real-time Avaya Aura components (CM, Session Manager, Media Server), Avaya strictly mandates a 1:1 ratio of vCPUs to physical cores.


Avaya allows these adjustments to get the VM running on slower hardware. However, if users open a support ticket for voice quality issues, lag, or dropped calls, 
Avaya Support may require them to move the VM to a host with a higher clock speed (e.g., Xeon Gold @ 2.6GHz+) before troubleshooting further.

https://support.avaya.com/css/public/documents/101087614

Attachment File


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy