Hi Richard I have been playing around with your lovely libguestfs tools . I have however run into a bit of a problem Basically I have a 5.4T qcow2 virtual disk, which I made too small (bugger) So I had read that you can expand these with your virt-resize tools. So I tried this sort of thing virt-resize --expand /dev/sda1 virtual.qcow2 outdisk.qcow2 however it gives me the rather intersting Fatal error: exception Guestfs.Error("febootstrap-supermin-helper exited with error status 1, see debug messages above") Which I took to be non-optimal I believe however this could mean that my cachedir is to piddling in size [root@space space]# virt-resize --expand /dev/sda1 virtual.qcow2 outdisk.qcow2 Examining virtual.qcow2 ... libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x1f827f0 libguestfs: trace: add_drive "virtual.qcow2" "readonly:true" libguestfs: trace: add_drive = 0 libguestfs: trace: add_drive "outdisk.qcow2" "readonly:false" libguestfs: trace: add_drive = 0 libguestfs: trace: launch libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: launch: attach-method=appliance libguestfs: launch: tmpdir=/tmp/libguestfsteWT6W libguestfs: launch: umask=0022 libguestfs: launch: euid=0 libguestfs: command: run: febootstrap-supermin-helper libguestfs: command: run: \ --verbose libguestfs: command: run: \ -f checksum libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d libguestfs: command: run: \ x86_64 supermin helper [00000ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) supermin helper [00000ms] inputs[0] = /usr/lib64/guestfs/supermin.d checking modpath /lib/modules/2.6.32-696.13.2.el6.x86_64 is a directory picked vmlinuz-2.6.32-696.13.2.el6.x86_64 because modpath /lib/modules/2.6.32-696.13.2.el6.x86_64 exists checking modpath /lib/modules/2.6.32-696.16.1.el6.x86_64 is a directory picked vmlinuz-2.6.32-696.16.1.el6.x86_64 because modpath /lib/modules/2.6.32-696.16.1.el6.x86_64 exists checking modpath /lib/modules/2.6.32-431.11.2.el6.x86_64 is a directory picked vmlinuz-2.6.32-431.11.2.el6.x86_64 because modpath /lib/modules/2.6.32-431.11.2.el6.x86_64 exists checking modpath /lib/modules/2.6.32-504.3.3.el6.x86_64 is a directory picked vmlinuz-2.6.32-504.3.3.el6.x86_64 because modpath /lib/modules/2.6.32-504.3.3.el6.x86_64 exists supermin helper [00000ms] finished creating kernel supermin helper [00000ms] visiting /usr/lib64/guestfs/supermin.d supermin helper [00000ms] visiting /usr/lib64/guestfs/supermin.d/base.img supermin helper [00000ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img supermin helper [00000ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles supermin helper [00022ms] visiting /usr/lib64/guestfs/supermin.d/init.img supermin helper [00022ms] visiting /usr/lib64/guestfs/supermin.d/udev-rules.img supermin helper [00022ms] adding kernel modules supermin helper [00055ms] finished creating appliance libguestfs: checksum of existing appliance: 9157ab378e1f61ccd23c368c72b4b1dd1131a5cbb309216a14de65c614223f62 libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" libguestfs: [00057ms] begin building supermin appliance libguestfs: [00057ms] run supermin-helper libguestfs: command: run: febootstrap-supermin-helper libguestfs: command: run: \ --verbose libguestfs: command: run: \ --copy-kernel libguestfs: command: run: \ -f ext2 libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d libguestfs: command: run: \ x86_64 libguestfs: command: run: \ /var/tmp/guestfs.S833dI/kernel libguestfs: command: run: \ /var/tmp/guestfs.S833dI/initrd libguestfs: command: run: \ /var/tmp/guestfs.S833dI/root supermin helper [00000ms] whitelist = (not specified), host_cpu = x86_64, kernel = /var/tmp/guestfs.S833dI/kernel, initrd = /var/tmp/guestfs.S833dI/initrd, appliance = /var/tmp/guestfs.S833dI/root supermin helper [00000ms] inputs[0] = /usr/lib64/guestfs/supermin.d checking modpath /lib/modules/2.6.32-696.13.2.el6.x86_64 is a directory picked vmlinuz-2.6.32-696.13.2.el6.x86_64 because modpath /lib/modules/2.6.32-696.13.2.el6.x86_64 exists checking modpath /lib/modules/2.6.32-696.16.1.el6.x86_64 is a directory picked vmlinuz-2.6.32-696.16.1.el6.x86_64 because modpath /lib/modules/2.6.32-696.16.1.el6.x86_64 exists checking modpath /lib/modules/2.6.32-431.11.2.el6.x86_64 is a directory picked vmlinuz-2.6.32-431.11.2.el6.x86_64 because modpath /lib/modules/2.6.32-431.11.2.el6.x86_64 exists checking modpath /lib/modules/2.6.32-504.3.3.el6.x86_64 is a directory picked vmlinuz-2.6.32-504.3.3.el6.x86_64 because modpath /lib/modules/2.6.32-504.3.3.el6.x86_64 exists supermin helper [00006ms] finished creating kernel febootstrap-supermin-helper: open: /lib/modules/2.6.32-696.16.1.el6.x86_64/modules.dep: No such file or directory

libguestfs: command: run: rm libguestfs: command: run: \ -rf /var/tmp/guestfs.S833dI libguestfs: trace: launch = -1 (error) Fatal error: exception Guestfs.Error("febootstrap-supermin-helper exited with error status 1, see debug messages above") libguestfs: trace: close libguestfs: closing guestfs handle 0x1f827f0 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsteWT6W So I guess my question is, can you tell virt-resize to use a different directory other than the paths you have set?? Is trying to extend a 5.4T disk a sensible thing to do? Are there other more interesting options?