backup-begin
Peter Krempa
pkrempa at redhat.com
Thu Apr 6 13:50:30 UTC 2023
On Wed, Apr 05, 2023 at 17:37:31 +0200, André Malm wrote:
> 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.
Huh, that is weird. Both images seem to be qcow2v3 so it's weird that
the code reaches the assertion.
I think at this point you should report an issue with qemu:
https://gitlab.com/qemu-project/qemu/-/issues
or report it on the qemu-block at nongnu.org mailing list
You'll be asked for what operations lead to the failure so please make
sure to collect the libvirt debug log as I've requested.
I can help the qemu team to analyze it so make sure to mention me (or my
gitlab handle 'pipo.sk') on the issue.
More information about the libvirt-users
mailing list