Description of problem: The amount of memory allocation is changed to the limit of maximum memory after creating a VM based on the XML file which dumped from a VM with changing amount of memory allocation. Version-Release number of selected component (if applicable): libvirt-0.1.7-2.src.rpm Version : 0.1.7 Release : 2 How reproducible: everytime Steps to Reproduce: 1.Start domain #virsh create /tmp/vm.xml 2.Change amount of memory allocation #virsh setmem 14 128000 3.Dump xml #virsh dumpxml > /tmp/vm1.xml 4.Stop domain #virsh shutdown vm 5.Start domain #virsh create /tmp/vm1.xml Actual results: The amount of memory allocation is changed to the limit of maximum memory after creating a VM based on the XML file which dumped from a VM with changing amount of memory allocation. Expected results: The amount of memory allocation is succeeded to after creating a VM based on the XML file which dumped from a VM with changing amount of memory allocation. Additional info: The XML file which I used is attached.
I have a patch for this, I just commited it upstream with extra regression tests. I checked, with a RHEL5b2 domu resized from 385Mb to 175Mb, the XML dump now says: <memory>394240</memory> <currentMemory>179200</currentMemory> and the domain is now recreated as expected, xm list --long says: (memory 175) (shadow_memory 0) (maxmem 385) So I guess this fixes it. Patch enclosed, however I have no garantee it will make RHEL5 GA, Daniel
Created attachment 140876 [details] patch for this bug
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Patch commited in libvirt upstream Daniel
QE ack for RHEL5.
Okay libvirt-0.1.8-6.el5 has been built with the fix, Daniel
Requesting exception for 5.0.0 --- patch and package both ready and waiting to go, and QA have approved testing.
A package has been built which should help the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.