Bug 1482041 - [Memory hotplug] Mismatching values and units in memory hotplug
Summary: [Memory hotplug] Mismatching values and units in memory hotplug
Keywords:
Status: CLOSED DUPLICATE of bug 1482042
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-16 10:41 UTC by Israel Pinto
Modified: 2017-08-16 12:32 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-16 12:32:17 UTC
oVirt Team: Virt
Embargoed:
ipinto: planning_ack?
ipinto: devel_ack?
ipinto: testing_ack?

Attachments (Terms of Use)
logs (707.05 KB, application/x-xz)
2017-08-16 10:41 UTC, Israel Pinto 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.