This is an automated cleanup. This bug report has been moved
to QEMU's new bug tracker on gitlab.com and thus gets marked
as 'expired' now. Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/58
** Changed in: qemu
Status: Incomplete => Expired
** Cha
my patches went in, ultimately, and my focus was since shifted
elsewhere. I just tried this by *manually* adding some extra data to a
bitmap by hand.
qemu-img create -f qcow2 foo.qcow2 64m
qemu-img bitmap --add foo.qcow2 mybitmap
This creates a bitmap extension header like this (starting at 0x1f
Sorry, that formatted *terribly*... please see the attachment for a raw
text version with arbitrarily long columns that looks nicer. :(
** Attachment added: "Raw text for comment #7 with better formatting (?)"
https://bugs.launchpad.net/qemu/+bug/1808928/+attachment/5490362/+files/bztemp
--
John, did you find some spare time to work on those patches that you've
mentioned? I.e. has this been addressed already?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bug
For now, QEMU cannot accept images with extra bitmap data, because QEMU
isn't aware of the semantics of those fields, so we cannot even allow
the image to load, just in case.
However, we SHOULD allow qemu-img check --repair to detect such bitmaps
as corruption so that images can be scrubbed and re
Sorry, because of log time, VM logs were removed. Journalctl for libvirtd is
remain.. It was like that.
018-12-17 17:01:50.990+: 43198: error : qemuMonitorIORead:606 : Unable to
read from monitor: Connection reset by peer
Dec 17 20:01:50 vm-kvm09 libvirtd[43198]: 2018-12-17 17:01:50.991+:
OK, I think it is a bug that you cannot at least repair the image,
though the cause of corruption is still unknown to me. Do you have
libvirt/QEMU logs from when then VM was shut down, before it wouldn't
boot properly again?
--
You received this bug notification because you are a member of qemu-
as far as i know nothing happened. it had worked normally while instance
was running. For a reason, instance is shutdown, then it never open
again. i have some backups, i tried to return previous backups. But they
also gave same error. Thanks to replication i could get it back. i
copied image from
Hi, bitmap extensions have a field that allows us to attach
extra/arbitrary data to them. It is not currently used by QEMU. If this
field is set, it means something corrupted your qcow2.
Please make a backup of your qcow2 file first (because attempting to
repair a broken qcow2 can sometimes make i
