Go to file
Stefan Reiter e9b36665c7 fix saving and loading dirty bitmaps in snapshots
Saving dirty bitmaps from our savevm-async code didn't work, since we
use a coroutine which holds the iothread mutex already (upstream savevm
is sync, migration uses a thread). Release the mutex before calling the
one function that (according to it's documentation) requires the lock to
*not* be held: qemu_savevm_state_pending.

Additionally, loading dirty bitmaps requires a call to
dirty_bitmap_mig_before_vm_start after "loadvm", which the upstream
savevm does explicitly afterwards - do that too.

This is exposed via the query-proxmox-support property
"pbs-dirty-bitmap-savevm".

Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
2021-03-16 20:44:06 +01:00
debian fix saving and loading dirty bitmaps in snapshots 2021-03-16 20:44:06 +01:00
keycodemapdb bump version to 3.0.0-1 2018-09-07 14:52:23 +02:00
qemu@553032db17 Update to QEMU 5.2 2021-02-12 10:20:01 +01:00
.gitmodules import stable-4 build files 2017-04-05 11:39:09 +02:00
backup.txt correct link to vma spec to new repository url 2020-01-14 11:18:52 +01:00
Makefile Update to QEMU 5.2 2021-02-12 10:20:01 +01:00
vma_spec.txt import stable-4 build files 2017-04-05 11:39:09 +02:00