Bug 251566
| Summary: | Trouble with booting 2.6.18-37.el5xen kernel on a Dell PowerEdge machine | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Gurhan Ozen <gozen> | ||||||||||||||||
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||||||
| Priority: | low | ||||||||||||||||||
| Version: | 5.1 | CC: | jburke | ||||||||||||||||
| 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: | 2007-09-25 12:53:01 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
Gurhan Ozen
2007-08-09 19:40:13 UTC
Created attachment 161010 [details]
xen kernel boot.
That kernel boot log is useless - please reboot *without* the 'quiet' option specified for the kernel. Can we also have a boot log from the non-Xen kernel for comparison - again with the 'quiet' option Created attachment 161011 [details]
dmidecode on the machine
Created attachment 161013 [details]
cpuinfo from the box
Created attachment 161014 [details]
lspci info from the machine
Created attachment 161015 [details]
meminfo of the machine
Created attachment 161016 [details]
xen kernel boot log
Created attachment 161019 [details]
boot log from non-xen kernel
(In reply to comment #3) > Can we also have a boot log from the non-Xen kernel for comparison - again with > the 'quiet' option Yes, i just attached both xen and non-xen kernel boot logs without the quiet option. Sorry about the quiet option, sometimes i forget about such defaults. Ok, so the kernel itself looks like its booting OK. The last set of messages Freeing unused kernel memory: 168k freed Write protecting the kernel read-only data: 360k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c Are right at the point where the initrd starts up. Normally you'd expect Freeing unused kernel memory: 192k freed Write protecting the kernel read-only data: 469k Red Hat nash version 5.1.19.6 starting Have you experianced the same problem on multiple different machines / installs ? Or is it perhaps just a messed up in the initrd that needs rebuilding ? Hmm no, i haven't seen this anywhere else. I can try to install on another identical machine or just re-install on the same machine. Rebuilt the initrd image but got the same result. Gurhan,
I just went through this with Dave Anderson. I'm fairly certain what
happened here is that you installed an i686 kernel on an x86_64 machine. I
would have expected it to actually blow up, but what it does is show the runaway
loop messages instead. I've pushed an RFC to rhkernel-list to try to detect
this situation and at least warn about it. Anyway, I'm pretty sure this isn't a
bug, so I'm going to close it as NOTABUG. Re-open if you have problems.
Chris Lalancette
|