I'm trying to use virt-sysprep for the first time, and getting the following error:
[root@ian ~]# virt-sysprep -d rdo-template Examining the guest ... Fatal error: exception Guestfs.Error("could not create appliance through libvirt: Unable to read from monitor: Connection reset by peer [code=38 domain=10]")
Digging into the qemu log, I see:
qemu-system-x86_64: -drive file=/var/lib/libvirt/images/rdo-template.img,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none: could not open disk image /var/lib/libvirt/images/rdo-template.img: Invalid argument
qemu-img -info says this about the file:
image: /var/lib/libvirt/images/rdo-template.img file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 1.3G cluster_size: 65536
Any ideas what's going on?
(libguestfs-tools-1.22.7-1.fc19.x86_64, BTW.)
On Thu, Oct 31, 2013 at 12:37:56PM -0500, Ian Pilcher wrote:
I'm trying to use virt-sysprep for the first time, and getting the following error:
[root@ian ~]# virt-sysprep -d rdo-template Examining the guest ... Fatal error: exception Guestfs.Error("could not create appliance through libvirt: Unable to read from monitor: Connection reset by peer [code=38 domain=10]")
Digging into the qemu log, I see:
qemu-system-x86_64: -drive file=/var/lib/libvirt/images/rdo-template.img,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none: could not open disk image /var/lib/libvirt/images/rdo-template.img: Invalid argument
qemu-img -info says this about the file:
image: /var/lib/libvirt/images/rdo-template.img file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 1.3G cluster_size: 65536
Any ideas what's going on?
(libguestfs-tools-1.22.7-1.fc19.x86_64, BTW.)
Sorry, I didn't see this email before now.
Unfortunately these qemu errors are very opaque. EINVAL could indicate a whole host of problems with the disk, perhaps an invalid format, disk corruption, or some backing file not being readable.
There is some effort upstream to get qemu to print better error messages.
Rich.
-
Ian Pilcher -
Richard W.M. Jones