Description of problem: After I was able to boot my guest as described in bz#499596, my guest fails again at startup. Changing drive interface from virtio to ide helps to boot. Version-Release number of selected component (if applicable): qemu-0.10-16.fc11.i586 kernel-2.6.29.2-126.fc11.i586 How reproducible: always for me Steps to Reproduce: 1. follow steps in https://bugzilla.redhat.com/show_bug.cgi?id=499596 2. run /usr/bin/qemu-kvm -cpu qemu32 -boot c -drive file=rawhide.img,if=virtio,index=0,boot=on -serial stdio Actual results: Initalizing network drop monitor service Freeing unused kernel memory: 436k freed Write protecting the kernel read-only data: 1460k Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 Nothing else on serial console. Expected results: booted system Additional info:
As glommer points out, this could be an extboot issue - with IDE, if extboot fails then boot can still succeed, but this is not true for virtio Also, note that this is a 32 bit host
After looking at the bug report in details, it is probably _not_ an extboot related issue. extboot only serves the purpose of booting the system. It seems this step is passed for this guy.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Does this still happen ?
Yes, still problem with qemu-0.10.4-5.fc11.i586.
Could you boot the guest in qemu and confirm that the initrd.img in /boot has the virtio drivers included? $> gzip -cd < /boot/initrd...img | cpio -ivt --quiet | grep virtio I think you installed without virtio originally, which would explain it. To fix that, you just need to run e.g. $> mkinitrd --with virtio_pci --with virtio_blk -f \ /boot/initrd-$(uname -r).img $(uname -r)
(In reply to comment #9) > Could you boot the guest in qemu and confirm that the initrd.img in /boot has > the virtio drivers included? > > $> gzip -cd < /boot/initrd...img | cpio -ivt --quiet | grep virtio Resulted with no output. > I think you installed without virtio originally, which would explain it. I think this was broken when I updated my kernel without virtio driver, because virtio was not functional for me in previous releases. Todays installation of Leonidas worked well. > To fix that, you just need to run e.g. > > $> mkinitrd --with virtio_pci --with virtio_blk -f \ > /boot/initrd-$(uname -r).img $(uname -r) This also fixed my problem. You can close this bug too.
Excellent, thanks