diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/zero-shot/108/other/2912 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/zero-shot/108/other/2912')
| -rw-r--r-- | results/classifier/zero-shot/108/other/2912 | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/2912 b/results/classifier/zero-shot/108/other/2912 new file mode 100644 index 00000000..93f46f09 --- /dev/null +++ b/results/classifier/zero-shot/108/other/2912 @@ -0,0 +1,28 @@ +device: 0.845 +graphic: 0.817 +vnc: 0.509 +semantic: 0.423 +boot: 0.309 +KVM: 0.275 +PID: 0.268 +debug: 0.204 +network: 0.182 +other: 0.168 +performance: 0.094 +files: 0.091 +socket: 0.090 +permissions: 0.065 + +qcow2 image corrupted after snapshot+bitmap action +Description of problem: +When taking a backup of the VM via snapshot + bitmap, the qcow2 image became corrupt: +`qcow2: Marking image as corrupt: Preventing invalid write on metadata (overlaps with bitmap directory); further corruption events will be suppressed` + +This resulted in a corrupt (unfix-able) image (see #2909). + +While this process is something that happens multiple times a day, we never hit any issue. +The underlying storage didn't report any error, so it seems like something inside qemu broke the image. +Steps to reproduce: +Unfortunately, I was unable to reproduce this issue yet. +Additional information: + |