Den 2023-04-05 kl. 09:47, skrev Peter Krempa:
The backup operation is quite complex so it is possible. Please have a look into /var/log/libvirt/qemu/$VMNAME.log to see whether qemu logged something like an assertion failure before crashing. Additionally you can have a look into 'coredumpctl' whether there are any recorded crashes of 'qemu-system-x86_64' and also possibly collect the backtrace. Also make sure to try updating the qemu package and see whether the bug reproduces. If yes, please collect the stack/back-trace, versions of qemu and libvirt, the contents of the VM log file and also ideally configure libvirt for debug logging and collect the debug log as well: https://www.libvirt.org/kbase/debuglogs.html
In the $VMNAME.log: qemu-system-x86_64: ../../block/qcow2.c:5175: qcow2_get_specific_info: Assertion `false' failed.
I'm running libvirt 8.0.0, which is the latest version for my dist (ubuntu 22.04). If required how would I properly upgrade?
Looking at https://github.com/qemu/qemu/blob/0c8022876f2183f93e23a7314862140c94ee62e7/block/qcow2.c which would be the version of qcow2.c for 8.0.0 there seem to be some issue with qcow2 compat.
I'm using qcow2 compat 1.1, output of qemu-img info of the base and top image;
qemu-img info base.qcow2 image: base.qcow2 file format: qcow2 virtual size: 5 GiB (5368709120 bytes) disk size: 1.9 GiB cluster_size: 65536 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false qemu-img info -U top.qcow2 image: top.qcow2 file format: qcow2 virtual size: 60 GiB (64424509440 bytes) disk size: 1.36 GiB cluster_size: 65536 backing file: base.qcow2 backing file format: qcow2 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false bitmaps: [0]: flags: [0]: in-use [1]: auto name: 1680670811 granularity: 65536 refcount bits: 16 corrupt: false extended l2: false
