|
Red Hat Bugzilla – Full Text Bug Listing |
| Summary: | F16 does not boot under Xen under D945GCLF2 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joerg <joerg> | ||||||||
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | berrange, jforbes, ketuzsezr, kraxel, m.a.young, virt-maint, xen-maint | ||||||||
| 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-03-23 09:27:57 EDT | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | ||||||||||
| Attachments: |
|
||||||||||
Did you look in http://wiki.xen.org/xenwiki/XenParavirtOps to follow the troubleshoot guide and capture some details? Do you get any details if you provide 'console=hvc0 debug loglevel=8' on the Linux line? And on the Xen hypervisor line youy have 'sync_console console_to_ring loglvl=all'? What hardware is this? Is there a reason for using acpi=ht? Hmm, this is not reassuring: (XEN) ERROR: Unable to locate IOAPIC for GSI 9 (XEN) No IOAPIC for GSI 9 What are the arguments for the Linux command line? Have you added some extra ones? Created attachment 534083 [details]
Initial logfile with boot options
Created attachment 534084 [details]
second logfile with requested boot options
This is a Intel D945GCLF2 Motherboard with 2 Atom CPUs. I have read in the net that my issue is related to acpi. So I have tried some options. My initial logfile was holding several attempts because I forgot to truncate it. I have attached one logfile with the boot options and the messages only from this attempt. A second file is attached with your requested options and the messages from this run. Interesting. There is another bug with an Atom machine not booting either- Bug #745961 that has the same exact error: [ 0.143986] reserve RAM buffer: 00000001097be000 - 000000010bffffff (XEN) domain_crash_sync called from entry.S (ff1d9724) (XEN) Domain 0 (vcpu#0) crashed on cpu#1: I found out that if I update the kernel to 3.2-rc1 it works just great. Great news ! But how do I update the kernel to 3.2-rc1 ? I cannot find that version in the repos. |
Created attachment 534053 [details] xen output captured via console=com1 Description of problem: Starting F16 kernel 3.1.1 under xen 4.1.2 does not work. After starting xen no additional messages are displayed. Version-Release number of selected component (if applicable): see above How reproducible: every time Steps to Reproduce: 1. install xen 2. choose f16 with xen in grub 3. Actual results: Nothing, no message at all, no automatic reboot Expected results: f16 running as dom0 Additional info: xen logfile attached