Interesting, it _looks_ like the instance crashed. I wonder if we can get the coredumps here.
We only see "blockdev-del" calls in the libvirt debug log. However, if a snapshot attempt _was_ really made, we should've also seen "blockdev-add" and "blockdev-snapshot-sync" calls. I'm wondering what's missing here. Perhaps we need more input from the libvirt/QEMU block layer devs
For context, check out the below related (resolved) bug:
# @blockdev-del:
#
# Deletes a block device that has been added using blockdev-add.
# The command will fail if the node is attached to a device or is
# otherwise being used.
Interesting, it _looks_ like the instance crashed. I wonder if we can get the coredumps here.
We only see "blockdev-del" calls in the libvirt debug log. However, if a snapshot attempt _was_ really made, we should've also seen "blockdev-add" and "blockdev- snapshot- sync" calls. I'm wondering what's missing here. Perhaps we need more input from the libvirt/QEMU block layer devs
For context, check out the below related (resolved) bug:
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1809409 — Failed to create volume from vm snapshot image
This was resolved via a libvirt fix in libvirt- 6.0.0-17. el8 (https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1820016). However the setup here is using libvirt-7.0.
Also, "blockdev-del" means, in QEMU language:
# @blockdev-del:
#
# Deletes a block device that has been added using blockdev-add.
# The command will fail if the node is attached to a device or is
# otherwise being used.