Description of problem: Suppose the memory value of "change allocation" and "maximum allocation" is both "1024". Modify the "change allocation" is "512", and it will be "1024" after the guest is powered on; Modify the "Maximum allocation" from "1024" to "2048", the value of "change allocation" and "maximum allocation" will be both "2048"; Then modify "change allocation" to "1024", apply, and modify "maximum allocation" to "1024", the value of "change allocation" and "maximum allocation" will also be "2048". This problem is not existed in rh6.1. Version-Release number of selected component (if applicable): libvirt-0.8.2-20.el5 virt-manager-0.6.1-14.el5 kernel-2.6.18-262.el5 How reproducible: always Steps to Reproduce: Suppose "CA" is the abbreviation of memory "change allocation"; and "MA" is the abbreviation of memory "maximum allocation". Suppose the original value of "CA" and "MA" of a gues is both "1024" 1.Modify "CA" and "MA" from "1024","1024" to "512" "1024"; 2.Modify "CA" and "MA" from "1024","1024" to "512" "2048"; 3.Modify "CA" and "MA" from "2048","2048" to "512" "512"; 3.Modify "CA" and "MA" from "2048","2048" to "512" "5120"; Actual results: 1. The value of "CA" and "MA" is "1024", "1024" 2. The value of "CA" and "MA" is "2048", "2048" 3. The value of "CA" and "MA" is "2048", "2048" 4. The value of "CA" and "MA" is "5120", "5120" Expected results: 1. The value of "CA" and "MA" is "512", "1024" 2. The value of "CA" and "MA" is "512", "2048" 3. The value of "CA" and "MA" is "512", "512" 4. The value of "CA" and "MA" is "512", "5120" Additional info:
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
*** Bug 712343 has been marked as a duplicate of this bug. ***
This seems like a libvirt bug. Starting with a shutoff qemu guest with 1024 MB for both memory and currentMemory, use virsh edit to change currentMemory to say 500000 KB. Change is accepted, verify that dumpxml shows correctly changed value. Start the guest, wait a couple seconds, shut it down. virsh dumpxml now shows currentMemory set to the previous 1024 MB value.
bug 737041 is a similar report against rhel 6