(In reply to Jiri Slaby from comment #17) > Or is this host-setup-specific (maybe virtio-blk) memory corruption or > something? Fabian, can you try with virtio-scsi instead of virtio-blk? Something like: -drive file=/data/libvirt/disks/boo1192714.qcow2,if=none,id=hd -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd Instead of: -blockdev driver=file,node-name=hd0-file,filename=/data/libvirt/disks/boo1192714.qcow2,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on -device virtio-blk,id=hd0-device,drive=hd0,serial=hd0