diff options
Diffstat (limited to 'results/classifier/zero-shot/105/device/2912')
| -rw-r--r-- | results/classifier/zero-shot/105/device/2912 | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/105/device/2912 b/results/classifier/zero-shot/105/device/2912 new file mode 100644 index 000000000..36c5f9399 --- /dev/null +++ b/results/classifier/zero-shot/105/device/2912 @@ -0,0 +1,26 @@ +device: 0.845 +graphic: 0.817 +vnc: 0.509 +instruction: 0.456 +semantic: 0.423 +boot: 0.309 +KVM: 0.275 +network: 0.182 +other: 0.168 +socket: 0.090 +mistranslation: 0.071 +assembly: 0.024 + +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: + |