Bug 683370
| Summary: | wrong kernel installed for 32-bit xenpv guests | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Jones <drjones> | ||||||
| Component: | anaconda | Assignee: | Will Woods <wwoods> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 14 | CC: | jonathan, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-16 16:37:06 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Andrew Jones
2011-03-09 09:46:00 UTC
Please attach /var/log/anaconda.* from the installed system to this bug report. Created attachment 484094 [details]
shar of all anaconda logs
The key line here is: 03:57:59,055 INFO anaconda: selected kernel package for kernel It looks to me like we didn't even try to get a kernel-PAE package, so there must be a problem with our isys.isPaeAvailable call. What does /proc/cmdline from within the VM look like? I can't boot the guest to look at it. I got the anaconda logs by loop back mounting the root fs. /proc/cmdline during the install isn't interesting, it's just method=http://download.englab.brq.redhat.com/pub/fedora/linux/releases/14/Fedora/i386/os console=hvc0 console=tty0 I added the 'console=tty0' to my virt-install command line in order to enable the use of virt-viewer, allowing Ctrl+Alt+F2. Ugh, sorry - I meant /proc/cpuinfo. I'm just too used to asking for the other one. The command line from the grub.conf of the installed/non-booting guest is kernel /vmlinuz-2.6.35.6-45.fc14.i686 ro root=UUID=ab8562fe-854a-40c0-9722-8e0a8ce87b8e rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=hvc0 rhgb quiet Created attachment 484234 [details]
screenshot of /proc/cpuinfo
Wow, surprised bugzilla didn't give me a collision warning with that simultaneous update...
Ok, here's /proc/cpuinfo (2 procs)
Going to have to step through this one to figure it out. /proc/cpuinfo looks good. I think wwoods was working on something along these lines. Yeah, that was bug 480031 (private, alas). In that bug, if you installed multiple kernels on a xen guest, the xen kernel wasn't getting set up as the *default* kernel in the resulting bootloader config. The relevant commit (for rhel5-branch) is: http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=84dcd103 but that's obviously not gonna help since we have no 'xen' kernel in Fedora. But the problem here isn't "too many kernels", it's "we picked the wrong one" - something wrong with package selection, not bootloader config. I have no clue if this will help, but I just tried installing a 32bit version of Fedora as a VM, also on Xen. Ran into the same problem in that it wouldn't boot. I managed to get it to boot by mounting the VM drive in my host, chrooting and installing a PAE enable kernel from Koji. I noticed two things: 1. /etc/sysconfig/kernel has kernel-PAE as the default kernel to update. 2. While it was chrooted (in my 64bit host), yum kept on telling me "No matches found for: kernel-PAE". I'm not sure if yum intelligently detected the 64bit or something like that, but just throwing it out there. Hopefully it helps. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |