summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/322602
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/322602
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/322602')
-rw-r--r--results/scraper/launchpad-without-comments/32260215
1 files changed, 15 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/322602 b/results/scraper/launchpad-without-comments/322602
new file mode 100644
index 000000000..e592ade9c
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/322602
@@ -0,0 +1,15 @@
+Snapshot usage makes qcow2 image unusable due to large tables
+
+To reproduce with 0.9.1 and svn:
+- Create a 20G (or some size much greater than system RAM) qcow2 image
+- Inside VM, install some OS, formatting whole drive
+- Create snapshot with savevm
+- Inside VM, reformat and reinstall OS
+- Create snapshot with savevm
+[...]
+
+Eventually, qemu crashes, then neither qemu-img nor qemu can open the image because memory is exhausted.  The reason is that the whole refcount_table is loaded into memory, and this refcount_table has now become much bigger than the size of memory.
+
+The refcount_table really needs to be loaded and used in fixed size chunks to avoid this problem.
+
+Alternatively, there needs to be a way to "rollback" a snapshot without loading the whole disk image normally, so that a snapshot which has made the image unusable in this way can be reversed.
\ No newline at end of file