Description of problem: the vm was started on 4.1 cluster and cannot be started on 4.2 because of: it seems there's odd max memory: -[ RECORD 1 ]------------------+---------------------------------------------------------------------------------------- vm_name | brq-openstack mem_size_mb | 2048 max_memory_size_mb | 4194304 (also visible in admin portal) changing max memory in admin portal solved the issue: -[ RECORD 1 ]------------------+---------------------------------------------------------------------------------------- vm_name | brq-openstack mem_size_mb | 2048 max_memory_size_mb | 16384 Version-Release number of selected component (if applicable): ovirt-engine-4.2.2.6-0.1.el7.noarch How reproducible: 1 in 1 Steps to Reproduce: 1. 2. 3. Actual results: a vm which got started in time of 4.1 cluster cannot run on 4.2 env now Expected results: should work Additional info:
Dup of https://bugzilla.redhat.com/show_bug.cgi?id=1557272 ?
(In reply to Yaniv Kaul from comment #2) > Dup of https://bugzilla.redhat.com/show_bug.cgi?id=1557272 ? Seems so, so after one month we still have the issue here.
*** This bug has been marked as a duplicate of bug 1557272 ***