On Thu, Jan 08, 2009 at 08:01:03AM -0600, Ryan Harper wrote: > I don't need the vmdk, but if there is some other repeatable process > that can trigger this for you, getting that will allow me to recreate > the issue myself. For example, installing Debian into a vmdk, reboot, > and then fsck'ing from inside the vm would trigger it. Finding some > sort of repeatable process that can trip the bug but without using any > of your specific data would be the best way to move forward with the > bug.
I can reproduce this when installing Debian lenny i386 (using the lenny rc1 install images from http://www.debian.org/devel/debian-installer/). The installer will complain of I/O problems when trying to mkfs(8) the filesystem and will prompt you to retry/ignore. Shortly thereafter, the domain kernel panics. Attached is the libvirt configuration; it's pretty straightforward and translates into this kvm(1) invocation: /usr/bin/kvm -S -M pc -m 512 -smp 1 -name scsi -monitor pty -boot n \ -drive file=/var/lib/libvirt/images/scsi.qcow,if=scsi,index=0 \ -net nic,macaddr=02:00:00:4d:58:13,vlan=0,model=e1000 \ -net tap,fd=11,script=,vlan=0,ifname=vnet0 \ -net nic,macaddr=02:00:00:23:7f:3d,vlan=1,model=e1000 \ -net tap,fd=13,script=,vlan=1,ifname=vnet1 \ -serial pty -parallel none -usb -vnc 0.0.0.0:0 john -- John Morrissey _o /\ ---- __o j...@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__
scsi.xml
Description: XML document
