summaryrefslogtreecommitdiffstats
path: root/savevm.c
Commit message (Collapse)AuthorAgeFilesLines
* toplevel: remove error handling from qemu_malloc() callers (Avi Kivity)aliguori2009-02-051-19/+0
| | | | | | | | Signed-off-by: Avi Kivity <avi@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6531 c046a42c-6fe2-441c-8c8c-71466251a162
* Fix handling of disk-only snapshots (Kevin Wolf)aliguori2008-12-111-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | When creating a snapshot with multiple qcow2 disks attached, the current behaviour is that qemu creates a disk snapshot on all of them and chooses one to write the VM state to. Despite having the state only in one image, loadvm tries to restore the VM state from the middle of nowhere if you run qemu a second time with only one of the other images attached. In the lucky case it will fail because there simply is no state, but it also can happen that it loads the state of a different snapshot (the one this new one is based upon). The fix is to write a zero VM state size to the images which don't contain the state, and check this in loadvm. I agree that you probably have to provoke such things intentionally to get in a state like this with qemu itself. However, with my second patch that adds snapshot support to qemu-img it could become a reasonable use case to have snapshots with and without VM states on the same image. Signed-off-by: Kevin Wolf <kwolf@suse.de> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5985 c046a42c-6fe2-441c-8c8c-71466251a162
* Split savevm code into savevm.caliguori2008-11-111-0/+1245
This is pure code motion. The savevm code is all common code so we can build it once and share the object with all executables. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5700 c046a42c-6fe2-441c-8c8c-71466251a162
OpenPOWER on IntegriCloud