Hide Forgot
Description of problem: This bug originally cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1172061 Following it's latest descriptions provided by me, I was failed to start ovirt-engine service as had no sufficient memory om my RHEVH. Please use all the steps provided in the original bug. 1172061 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1014289 [details] hs_error.log
Created attachment 1014290 [details] logs from host and engine's VM
Original bug included in comment #0 is targeted to 3.5.3. Re-targeting to the same release. Re-assigning to fabian and moving to node team. Setting the component to rhevm-appliance since the ram allocated for the VM is defined in the OVA.
Nikolai, in bug 1172061 comment 23 I asked you about the symptom in bug 1172061 comment 18: OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000b0000000, 357892096, 0) failed; error='Cannot allocate memory' (errno=12) # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 357892096 bytes for committing reserved memory. # An error report file with more information is saved as: # /tmp/jvm-14225/hs_error.log /var/log/ovirt-engine/console.log (END) Does this bug still exist with the new RHEV-M appliance?
Thanks Nikolai! To me that looks as if the bug in comment 5 is indeed fixed, thus I am closing this bug. Could you please open a separate bug for the suboptimal ssh configuration in comment 16?
Cloned to https://bugzilla.redhat.com/show_bug.cgi?id=1218312.
(In reply to Fabian Deutsch from comment #18) > Thanks Nikolai! > > To me that looks as if the bug in comment 5 is indeed fixed, thus I am > closing this bug. > > Could you please open a separate bug for the suboptimal ssh configuration in > comment 16? Please set target release accordingly, 3.5.4 is not yet released.