Bug 250620
| Summary: | F7: kvm gives exception 13 when starting | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sirius Rayner-Karlsson <akarlsso> |
| Component: | kvm | Assignee: | Glauber Costa <gcosta> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7 | CC: | avi, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-17 02:04:39 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: | |||
|
Description
Sirius Rayner-Karlsson
2007-08-02 14:25:00 UTC
Can you test with kvm-33 from kvm.qumranet.com (both kernel module and userspace)? kvm-24 is a bit old. Additionally, what is in that vm? A Fedora variant? I will test with kvm-33 as you suggest, but I am having trouble connecting to kvm.qumranet.com to view the FAQ at the moment. Will keep trying. I have available to install RHEL3.9, RHEL4.5, RHEL5.0, FC6 and F7 into that VM. Nothing is installed right now, I am trying to install it for work purposes though. Additional info, I can start qemu-kvm if I specify kernel and initrd to use. Not found any other means to start it yet though. Have now tested with kvm-33. It now boots, but will now not do PXE. Will do more testing tomorrow. Further testing with kvm-33 show that it mostly works. Netboot (PXE) does not work though. Thank you for pointing me at kvm-33. What can I do to assist in getting the netboot facility working again? Thanks! does netboot work with regular qemu? how is it failing with kvm? Netboot works with regular qemu, albeit painfully slowly. Using the command # /usr/bin/qemu-system-x86_64 -m 256 -net nic -net tap /dev/X60sVG/virt_vm -boot n It boots, and starts loading /pxelinux.0 With kvm, it just ignores the '-boot n' option and goes straight to disk. If the disk is not installed yet, it will just fail to boot. hmm. Can you use the -L option to direct qemu to use the kvm bios? That will tell us if that's the source of the problem. Tried the following combinations: # /usr/local/bin/qemu-system-x86_64 -M pc -m 256 -net nic -net tap /dev/X60sVG/virt_vm -boot n -L /usr/local/share/qemu/ This does not PXE boot. # /usr/bin/qemu-system-x86_64 -M pc -m 256 -net nic -net tap /dev/X60sVG/virt_vm -boot n -L /usr/local/share/qemu/ This does PXE boot. # /usr/local/bin/qemu-system-x86_64 -M pc -m 256 -net nic -net tap /dev/X60sVG/virt_vm -boot n -L /usr/share/qemu/ This does not PXE boot. # /usr/bin/qemu-system-x86_64 -M pc -m 256 -net nic -net tap /dev/X60sVG/virt_vm -boot n -L /usr/share/qemu/ This does PXE boot. Would you like me to run any other combinations? *** Bug 314241 has been marked as a duplicate of this bug. *** Some of my experiences; I replaced kvm-35 with kvm-36-6.fc8 and the problem still persist. (Only change is that I am presented a boot menu, which lacks network boot. No matter what I select the abort() hapens -- I assume the PXE ROM images get loaded after that.) Network boot has been fixed in kvm-38; so kvm-44 (the current version) should work. btw, the title of this bug report is now misleading. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |