Description of problem:
Making changes to CPU or memory without making other changes to the VM in virt-manager for KVM based guest persists as long as virt-manager is running. These changes are not written to /etc/libvirt/qemu/*.xml. If OTHER changes are made and saved, such as disconnecting a CD image from the CDROM or changing boot options, then the CPU and memory options will be saved as well.
Therefore, if you make changes to CPU and memory within virt-manager without making other changes to the VM, these changes will not persist across restarts of virt-manager, much less the OS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make sure the VM is not running
2. Make changes to the VM's CPU and/or memory
3. Boot the VM, and verify it is using the new CPU and/or memory settings
4. Check /etc/libvirt/qemu/*.xml for the host, and note that the CPU and/or memory settings have not changed.
5. Shut down the VM.
6. Change another hardware option not related to CPU or memory.
7. Check /etclibvirt/qemu/*.xml, and note that the CPU and/or memory setting are now saved, along with the other hardware option you changed.
CPU and memory options are not saved when done alone.
All changes to VM hardware settings should be saved.
After step 2 (before you start the VM) running virsh dumpxml <domid> does show the new, correct data.
Kyle, please can you post your virt-manager log
Created attachment 360210 [details]
virt-manager.log from the test system
Created attachment 378658 [details]
Make CPU + Mem changes persistent
This also solves bz 539496, so the change is a bit more complicated then required to fix just this bug.
Fix built in virt-manager-0_6_1-10_el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.