Bug 172079
Summary: | xen kernel panic | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
Component: | xen | Assignee: | Rik van Riel <riel> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | sct |
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: | 2006-01-18 18:09:16 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
Need Real Name
2005-10-30 22:17:07 UTC
This is still broken, and fc5t1 is frozen now. Please could you tell me what the problem? Lack of interest. Do you want this closed? There has been a significant rebasing of the kernel and HV images for fc5t2. Can you still reproduce the problem? If so, then this sounds like a mismatch between the memory calculations in the HV/bootloader and the kernel. The full Xen logs would be really useful in tracking this down; is it possible for you to capture that to a serial console? That, in conjunction with the normal non-xen boot logs, should let us examine the memory maps being computed in both cases to see if there's a mismatch somewhere. You _may_ be able to work around this by adding the "dom0_mem=...M" option to the xen hypervisor line ("kernel=xen...") in /etc/grub.conf. If you assign (say) only half your physical memory to dom0 on boot, does that work? There are a number of other reports of this in bug 172406: I'll close this one as a dup to keep the majority of the reports in one place. Please followup in the other bug report. *** This bug has been marked as a duplicate of 172406 *** |