Bug 996488 - Can't configure host with more than 2TB memory
Can't configure host with more than 2TB memory
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Depends On:
  Show dependency treegraph
Reported: 2013-08-13 05:28 EDT by Aharon Canan
Modified: 2013-08-13 07:54 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-13 07:54:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs (1.40 MB, application/x-gzip)
2013-08-13 05:39 EDT, Aharon Canan
no flags Details

  None (edit)
Description Aharon Canan 2013-08-13 05:28:56 EDT
Description of problem:
Can't configure host with more than 2TB memory

Version-Release number of selected component (if applicable):
3.2.2 (sf19.2)

How reproducible:

Steps to Reproduce:
1. configure RHEV with 2 hosts
2. in /usr/share/vdsm/caps.py set caps['memSize'] = '2147483648'
3. restart vdsm process

Actual results:
host become non-responsive

Expected results:
host should be up

from engine.log
2013-08-13 10:50:22,560 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (QuartzScheduler_Worker-64) Failed to parse memSize value 2147483648 to integer: java.lang.NumberFormatException: For input string: "2147483648"

Changes made in /usr/share/vdsm/caps.py
    caps['memSize'] = str(utils.readMemInfo()['MemTotal'] / 1024)
    #caps['memSize'] = '3221225472'
    caps['memSize'] = '2147483648'
Comment 1 Aharon Canan 2013-08-13 05:39:12 EDT
Created attachment 786094 [details]
Comment 2 Aharon Canan 2013-08-13 07:54:49 EDT
by mistake we set the memSize in KB instead of MB.
as from the code you can see it gets the value in KB but split by 1024.

we need to set memSize(KB)/1024

Note You need to log in before you can comment on or make changes to this bug.