Hide Forgot
Description of problem: Created from comment #11 of original https://bugzilla.redhat.com/show_bug.cgi?id=1299526. The new engine VM should have the same amount of memory as the physical host we migrate from. In case that HE-VM should have lesser RAM than original host, then /etc/ovirt-engine/engine.conf.d/10-setup-java.conf should be edited accordingly, so min and max values won't overpass the total RAM available for the HE-VM and they should be not larger than 25% of totally available RAM for the particular HE-VM. Version-Release number of selected component (if applicable): rhevm-3.6.2.5-0.1.el6.noarch jasperreports-server-pro-6.0.1-1.el6ev.noarch ovirt-vmconsole-proxy-1.0.0-1.el6ev.noarch ovirt-engine-extension-aaa-jdbc-1.0.5-1.el6ev.noarch rhevm-dwh-3.6.2-1.el6ev.noarch rhevm-dwh-setup-3.6.2-1.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1.Migrate barebone RHEVM to HE-VM. 2. 3. Actual results: If RAM available on HE-VM lesser than RAM on original barebone host, then "Starting oVirt Engine: [FAILED]" on host. Expected results: Starting oVirt Engine: [PASS]
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
It's not hosted-engine specific, it could also affects migrating from a phisical system to another with less RAM.
This update was published here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/self-hosted_engine_guide/#chap-Migrating_from_Bare_Metal_to_a_RHEL-Based_Self-Hosted_Environment Moving to CLOSED.