Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1320579

Summary: [Docs] The new engine VM should have the same amount of memory as the physical host we migrate from.
Product: Red Hat Enterprise Virtualization Manager Reporter: Nikolai Sednev <nsednev>
Component: DocumentationAssignee: Zac Dover <zdover>
Status: CLOSED CURRENTRELEASE QA Contact: Tahlia Richardson <trichard>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: adahms, dfediuck, eedri, gklein, lbopf, lsurette, mkalinin, rbalakri, srevivo, stirabos, ykaul, ylavi, zdover
Target Milestone: ovirt-4.0.6Keywords: Triaged, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-29 11:08:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nikolai Sednev 2016-03-23 14:30:29 UTC
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]

Comment 1 Yaniv Lavi 2016-05-09 11:01:49 UTC
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.

Comment 4 Simone Tiraboschi 2016-09-21 12:26:31 UTC
It's not hosted-engine specific, it could also affects migrating from a phisical system to another with less RAM.