search for: pull4

...'t give enough information. Please run 'qemu-img info' on those files and look for the 'backing file format:'field. That field is important, because otherwise we'd fall back to image format detection which was deemed unsafe and libvirt no longer allows it. $ qemu-img info pull4.qcow2 image: pull4.qcow2 file format: qcow2 virtual size: 10 MiB (10485760 bytes) disk size: 196 KiB cluster_size: 65536 backing file: pull3.qcow2 backing file format: qcow2 ^^^^^^^^^^^^^^^^^^^^^^^^^^ Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16...

Hi guys, I had to move to the new laptop week ago and I screw migration of my virtual machines. I recovered my virtual machines on the new laptop (virsh define) using the backed up xml files, but I am missing any file with metadata about snapshots. The original storage is cleaned so I cannot take these files anymore. Using qemu-info I can see my snapshots inside the qcow images, but libvirt

Hello list, upon upgrading from libvirt v5.9.0 -> v5.10.0, libvirt started calling qemu differently causing the VM operating system to not be found. I'm wondering whether I'm chasing a bug, or have to otherwise fix my domain config (created by virt-manager). To start with, I have a Windows 7 domain based on the following images: windows7-base.qcow2: QEMU QCOW2 Image (v3),

...roller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <---- these conform to the table above <driver name='qemu' type='qcow2'/> <source file='/tmp/pull4.qcow2'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </disk> <disk type='file' device='disk'> &...