After a hypervisor reboot some HA VMs fail to restart and encounter the error ACTION_TYPE_FAILED_VDS_VM_MEMORY

Solution Verified - Updated -

Issue

  • We have configured the HA settings for 3 VMs running on a single hypervisor configured for Local Storage. When the hypervisor is unexpectedly power cycled not all of the HA configured VMs power up. After testing 5 power cycles, no more than 2 of the 3 HA VMs came back up with no user intervention.
  • The ACTION_TYPE_FAILED_VDS_VM_MEMORY is observed in the /var/log/ovirt-engine/engine.log file when trying to start some of the HA VMs:
2013-03-08 13:18:49,329 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (QuartzScheduler_Worker-12) [2827fd89] Lock Acquired to object EngineLock [exclusiveLocks= key: ffc28047-d991-4b06-9c06-fc610c13ac4f value: VM
, sharedLocks= ]
...
2013-03-08 13:18:49,417 WARN  [org.ovirt.engine.core.bll.RunVmCommand] (QuartzScheduler_Worker-12) [2827fd89] CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_VDS_VM_MEMORY
  • Manually clicking on the VM and starting it works with no errors.

Environment

  • Red Hat Enterprise Virtualization 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.