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

Bug 1482041

Summary: [Memory hotplug] Mismatching values and units in memory hotplug
Product: [oVirt] ovirt-engine Reporter: Israel Pinto <ipinto>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs
Target Milestone: ---Flags: ipinto: planning_ack?
ipinto: devel_ack?
ipinto: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-16 12:32:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Israel Pinto 2017-08-16 10:41:13 UTC 
Created attachment 1314054 [details]
logs

Description of problem:
While hotplug memory to VM there is mismatch of value and units in the dimm device.

Version-Release number of selected component (if applicable):
Software version:4.2.0-0.0.master.20170813134654.gitaee967b.el7.centos

How reproducible:
All the time

Steps to Reproduce:
1. Create VM with OS
2. Start VM 
3. Hotplug memory in different sizes: 256M , 512MB, 1 GB couple of time each one.
and check VM device.  
See test case: https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM-22160

Actual results:
Memory is increased on the and update in General Tab.
But the sizes in VM device show different behavior then in 4.1.
That could expect Memory hot unplug. 
The values and units are not match with the value i hotplug.
   

Additional info:
See attached:
1. Snapshot of VM devices from 4.1 with same values   
2. Snapshot of VM devices from 4.2 
3. VM dumpxml
And logs
Comment 1 Israel Pinto 2017-08-16 12:32:17 UTC 

*** This bug has been marked as a duplicate of bug 1482042 ***