Bug 996488 - Can't configure host with more than 2TB memory
Summary: Can't configure host with more than 2TB memory
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-13 09:28 UTC by Aharon Canan
Modified: 2013-08-13 11:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-13 11:54:49 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

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

Description Aharon Canan 2013-08-13 09:28:56 UTC 
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:
100%

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 09:39:12 UTC 
Created attachment 786094 [details]
logs
Comment 2 Aharon Canan 2013-08-13 11:54:49 UTC 
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.