Bug 499601
Summary: | KVM guest fails to boot with if=virtio; works with if=ide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan ONDREJ <ondrejj> |
Component: | qemu | Assignee: | Glauber Costa <gcosta> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rawhide | CC: | dwmw2, gcosta, markmc, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-04 13:22:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 480594 |
Description
Jan ONDREJ
2009-05-07 11:58:07 UTC
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. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. 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 |