summaryrefslogtreecommitdiff
path: root/Using Libvirt to manage QEMU image bitmaps.md
diff options
context:
space:
mode:
authorJasper Ras <jaspert.ras@gmail.com>2025-04-18 21:01:49 +0200
committerJasper Ras <jaspert.ras@gmail.com>2025-04-18 21:01:49 +0200
commita8a8e1f984f20c8008f3a5f57cd39b416eb73104 (patch)
tree2262794b52d82c5fd9cbc55b503b52fafbd3af8a /Using Libvirt to manage QEMU image bitmaps.md
parent5fa69499917fab7a026c90c8321dbcc22734106a (diff)
parentab409a3701bf59dd73dc1e0324376bdac8b6d74f (diff)
vault backup: 2025-04-18 21:01:49
Diffstat (limited to 'Using Libvirt to manage QEMU image bitmaps.md')
-rw-r--r--Using Libvirt to manage QEMU image bitmaps.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/Using Libvirt to manage QEMU image bitmaps.md b/Using Libvirt to manage QEMU image bitmaps.md
new file mode 100644
index 0000000..72942b3
--- /dev/null
+++ b/Using Libvirt to manage QEMU image bitmaps.md
@@ -0,0 +1,29 @@
+---
+tags:
+ - qemu
+ - libvirt
+---
+To query info about block devices, including bitmaps we can use a QMP command:
+```
+sudo virsh qemu-monitor-command --pretty instance-00026133 '{"execute": "query-block", "arguments": {}}'
+```
+
+There are six primary bitmap-management API commands:
+- `block-dirty-bitmap-add`
+- `block-dirty-bitmap-remove`
+- `block-dirty-bitmap-clear`
+- `block-dirty-bitmap-disable`
+- `block-dirty-bitmap-enable`
+- `block-dirty-bitmap-merge`
+And one related query command:
+- `query-block`
+
+The `node` argument to bitmap cmds can be found as `node-name` in `query-block` results.
+
+
+#### Removing a dirty bitmap
+Cannot be removed if it is busy.
+Arguments: node, nameg
+
+---
+https://qemu-project.gitlab.io/qemu/interop/bitmaps.html \ No newline at end of file