See attachment for full logs. Appears at first glance to be related to the lack of support for virtio-net in the guest kernel. /usr/bin/qemu-kvm /usr/bin/qemu-kvm -drive file=test1.img,cache=off,if=ide -drive file=test2.img,cache=off,if=ide -drive file=test3.img,cache=off,if=ide -drive file=../images/test.sqsh,snapshot=on,if=ide -m 500 -no-reboot -kernel /tmp/libguestfscfrLMf/kernel -initrd /tmp/libguestfscfrLMf/initrd -append panic=1 console=ttyS0 guestfs=10.0.2.4:6666 guestfs_verbose=1 noapic -nographic -serial stdio -net channel,6666:unix:/tmp/libguestfscfrLMf/sock,server,nowait -net user,vlan=0 -net nic,model=virtio,vlan=0 -no-hpet -rtc-td-hack [...] SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCADDRT: No such process Reading all physical volumes. This may take a while... /init: line 48: /sys/block/vd*/queue/rotational: No such file or directory verbose daemon enabled connect: Network is unreachable connection to 10.0.2.4:6666 failed Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: guestfsd Not tainted 2.6.30 #1 Call Trace: [<ffffffff8023a51f>] panic+0xe0/0x190 [<ffffffff8023c044>] ? put_files_struct+0xac/0xb9 [<ffffffff802427af>] ? exit_ptrace+0x2f/0x112 [<ffffffff8023d296>] do_exit+0x7e/0x668 [<ffffffff8023d8f8>] do_group_exit+0x78/0xa8 [<ffffffff8023d93f>] sys_exit_group+0x17/0x1b [<ffffffff8020bbdb>] system_call_fastpath+0x16/0x1b Rebooting in 1 seconds..sock_read_event: 0x62d010 g->state = 1, fd = 3, events = 0x1 stdout_event: 0x62d010: child process died guestfs_wait_ready failed, see earlier error messages guestfs_wait_ready FAILED closing guestfs handle 0x62d010 (state 0) FAIL: tests