[Please keep replies on the mailing list so that others can benefit from following the discussion] On Fri, Oct 06, 2017 at 06:04:46AM +0000, emlyn.jose(a)wipro.com wrote: Don't use ‘--with-qemu=...qemu-img’, it is simply wrong. The --with-qemu parameter is intended to specify the hypervisor, and qemu-img is not a hypervisor. qemu-img comes from the PATH, see: https://github.com/libguestfs/libguestfs/blob/master/lib/create.c#L317 https://github.com/libguestfs/libguestfs/blob/master/lib/info.c#L194 External commands run through the guestfs_int_cmd_* mechanism can be displayed by enabling debugging: http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs so I suggest you enable this to see exactly what's going on. You just said above that you set the PATH to contain both qemu-kvm and qemu-img. Anyway, I suggest you enable debugging which will show you exactly what libguestfs is doing. Also don't put qemu-img into the ‘./configure --with-qemu’ parameter. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/