Yes I still have this problem, and I have a machine I can do testing on if you have anything for me to do. There were a few updates that just came in (listed below), and I tried saving all running VMs before the updates (hit the 1MB/s save issue) then the restore failed. So needless to say that didn't go well :/
I did dump the xml to a file then edit the running config via virsh. But issuing a restore after that wipes the config. I understand what you are saying about editing after doing the restore, but then how to you get the vm reset to use that config while it is "running" and churning at 100% CPU? I assume a destroy ruins the point of the restore, no?
Ubuntu 10.04.3 LTS
Yes I still have this problem, and I have a machine I can do testing on if you have anything for me to do. There were a few updates that just came in (listed below), and I tried saving all running VMs before the updates (hit the 1MB/s save issue) then the restore failed. So needless to say that didn't go well :/
lucid-updates/main x11-common 1:7.5+5ubuntu1.1 noroms- 0ubuntu9. 17 noroms- 0ubuntu9. 17 0ubuntu16+ 0.12.3+ noroms+ 0ubuntu9. 17
lucid-updates/main qemu-common 0.12.3+
lucid-updates/main qemu-kvm 0.12.3+
lucid-updates/main kvm 1:84+dfsg-
I did dump the xml to a file then edit the running config via virsh. But issuing a restore after that wipes the config. I understand what you are saying about editing after doing the restore, but then how to you get the vm reset to use that config while it is "running" and churning at 100% CPU? I assume a destroy ruins the point of the restore, no?