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

Bug 1639263

Summary: [downstream clone - 4.2.7] VM fails to start if maxMemory >= 2048 GB
Product: Red Hat Enterprise Virtualization Manager Reporter: RHV bug bot <rhv-bugzilla-bot>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.6CC: ahadas, apinnick, danken, lveyde, mavital, michal.skrivanek, ratamir, rbarry, Rhev-m-bugs
Target Milestone: ovirt-4.2.7Keywords: ZStream
Target Release: ---Flags: lsvaty: testing_plan_complete-
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.7.3 Doc Type: Bug Fix
Doc Text:
The current release supports virtual machines with 2 or more TB of memory.
 Story Points: ---
Clone Of: 1638124 Environment:
Last Closed: 2018-11-05 15:03:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1638124    
Bug Blocks:    

Description RHV bug bot 2018-10-15 12:26:00 UTC 
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1638124 +++
======================================================================

Description of problem:

If a maximum memory is configured >= 2048 GB, then a negative value is generated for the maxMemory.

===
2018-10-10 14:48:51,242-04 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-80) [d870c8c6-95c2-4690-81b0-2c7786d89a3a] VM <?xml version="1.0" encoding="UTF-8"?><domain type="kvm" xmlns:ovirt-tune="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0">
  <name>RHEL_7.4</name>
  <uuid>6c4da374-ed44-4407-943b-192d6b7ed540</uuid>
  <memory>1572864</memory>
  <currentMemory>1572864</currentMemory>
  <iothreads>1</iothreads>
  <maxMemory slots="16">-2147483648</maxMemory>       => negative value
===

Because of this, VM will fail to start with the error below.

2018-10-10 14:48:53,834-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-6) [] EVENT_ID: VM_DOWN_ERROR(119), VM RHEL_7.4 is down with error. Exit message: XML error: Invalid value '-2147483648' for element or attribute './maxMemory[1]'.


Version-Release number of selected component (if applicable):

ovirt-engine-4.2.6.4-0.1.el7ev.noarch

How reproducible:

100%

Steps to Reproduce:

1. Create a VM with Maximum memory >= 2048 GB and start it.


Actual results:

VM fails to start with error "XML error: Invalid value '-2147483648' for element or attribute './maxMemory[1]"

Expected results:

VM should start.

Additional info:

(Originally by Nijin Ashok)
Comment 1 RHV bug bot 2018-10-15 12:26:05 UTC 
Meital,

Please retest on 4.2.7 and mark this as a blocker in case it reproduce

(Originally by Raz Tamir)
Comment 3 RHV bug bot 2018-10-15 12:26:12 UTC 
Meital,

Please retest on 4.2.7 and mark this as a blocker in case it reproduce

(Originally by Raz Tamir)
Comment 4 RHV bug bot 2018-10-15 12:26:15 UTC 
we succeed to reproduce it On 4.2.7

(Originally by Meital Avital)
Comment 8 meital avital 2018-10-22 16:05:16 UTC 
Verified on:
ovirt-engine-4.2.7.3-0.1.el7ev
qemu-kvm-rhev-2.12.0-18.el7_6.1.x86_64
sanlock-3.6.0-1.el7.x86_64
libvirt-client-4.5.0-10.el7_6.2.x86_64
vdsm-4.20.43-1.el7ev.x86_64
Comment 12 errata-xmlrpc 2018-11-05 15:03:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3480
Comment 13 Daniel Gur 2019-08-28 13:12:23 UTC 
sync2jira
Comment 14 Daniel Gur 2019-08-28 13:16:35 UTC 
sync2jira