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
[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
Digging into the qemu log, I see:
could not open disk image /var/lib/libvirt/images/rdo-template.img:
qemu-img -info says this about the file:
file format: qcow2
virtual size: 8.0G (8589934592 bytes)
disk size: 1.3G
Any ideas what's going on?
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
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org