>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. Yes this is clear now. Thank you! > 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. Yes, I exported PATH correctly and is pointing to where I wanted but look at the log below after enabling the debugging that shows path of qemu-kvm and qemu-img. They are different. libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libguestfs: command: run: \ -o backing_file=/root/image123.tmp libguestfs: command: run: \ /tmp/libguestfs123/overlay1 Formatting '/tmp/…… ----- ------ libguestfs: [00000ms] begin testing qemu features libguestfs: command: run: /opt/qemu/bin/qemu-kvm libguestfs: command: run: \ -display none libguestfs: command: run: \ -help Does this mean that they are both taken from the same location?