Package: kvm Version: 72+dfsg-5~lenny1 Severity: important Sometimes, rebooting a kvm guest panics early in booting: RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 32768) 8388608 invalid compressed format (err=1) List of all partitions: No filesystem cound mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I have seen this problem after a kernel update in the guest. Most of the time, I can trigger it by rebuilding the initrd of the newest kernel installed, e.g.: dpkg-reconfigure linux-image-2.6.26-2-686 init 6 I can then kill the kvm process and start a new one, and it boots happily. I tried a lenny guest (i386) on a lenny host (amd64), with an IDE drive (hda), not virtio_blk (vda). virtio_blk is nice, but I have to support IDE because there are guests here without virtio_blk. Downgrading kvm to version 72+dfsg-4 solves this problem for me. So it looks like the fix for bug #506972 (debian/patches/restore_option_roms.patch: "fix hang on reboot with virtio") introduced a regression. I googled a bit and stumpled upon this, maybe it is related: http://osdir.com/ml/fedora-extras-commits/2009-05/msg03765.html I thought it might be a good idea to put some people in cc that were involved in the mentioned bug, I hope this is ok for them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
