Description of problem: At the moment minimum amount of ram for hosted engine VM defaults to 4096 MB Please specify the memory size of the VM in MB [Defaults to minimum requirement: 4096 MB if VM with 4096MB RAM is created engine-setup complaints that machine has less than recommended minimum amount of RAM (4096MB) for running engine (system can see only 3830MB RAM) Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.36.beta1.el6ev How reproducible: always Steps to Reproduce: 1.install self hosted engine 2. when asked about amount of RAM for VM with hosted engine use default minimum Actual results: engine-setup complaints about lack of RAM Expected results: VM for engine is by default created with enough RAM for engine-setup Additional info: complete deploy procedure http://www.ovirt.org/Hosted_Engine_Howto#Fresh_Install
It seems that the amount of RAM visible from inside the VM has changed from the past. engine-setup (from rhevm-setup package) is checking for 4096MB as minimum with a 5% of tolerance. So minimum should have been something like 3891. System now can see only 3830MB RAM so qemu is showing less RAM than before. Is this a wanted change in qemu or a regression in it? If it's something we want to support anyway, we should change the check in engine-setup, not requiring more ram in ovirt-hosted-engine-setup.
I have to admit that I do not know how MemTotal in /proc/meminfo is computed, but certainly it does not return the amount of physical memory, also on bare metal. You probably need to modify this check.
(In reply to Ronen Hod from comment #2) > I have to admit that I do not know how MemTotal in /proc/meminfo is > computed, but certainly it does not return the amount of physical memory, > also on bare metal. > You probably need to modify this check. MemTotal is ~= physical - reserved I think we can't rely on physical (dmidecode --type=17) because admin may limit memory usage by kernel command line. I think we can just use a 10% tolerance here instead of 5%. Unless someone can provide a real number under which the application won't work anyway. If this is accepted, this is an EasyFix.
Acking the fix. Would be nice to understand why this changed though - was there a difference in the amount of RAM reserved for QXL?
patch merged on upstream master and 3.3 branch
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step.