Bug 458808
| Summary: | xen crash during boot, auto reboot, xen crash during boot, auto reboot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Summerfield <debian> |
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 10 | CC: | berrange, linux.ninja1, markmc, virt-maint |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-18 06:18:02 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
John Summerfield
2008-08-12 13:55:53 UTC
I suppose I should mention this:
title Fedora (2.6.26-0.1.rc6.git2.fc10.x86_64.xen)
root (hd0,4)
kernel /xen.gz-2.6.26-0.1.rc6.git2.fc10.x86_64.xen com1=115200,8n1 conso
le=com1 `xencons=ttyS sync_console
# kernel /xen.gz-2.6.26-0.1.rc6.git2.fc10.x86_64.xen vga=text-80x60 com1=1
15200,8n1
module /vmlinuz-2.6.26-0.1.rc6.git2.fc10.x86_64.xen ro root=/dev/VolGrou
p00/LogVol00 vga=794 video=vesafb selinux=0 console=ttyS0,115200n8 console=tty
savedefault
module /initrd-2.6.26-0.1.rc6.git2.fc10.x86_64.xen.img
so you know I'm using the latest (atm) version.
*** This bug has been marked as a duplicate of bug 437930 *** I am reopening this as I don't see that it's related to 437930. This is xen, not the Linux kernel. It's not getting to the kernel. This is F9 no more. 437930 is supposed to be fixed RSN and before F10. Whether its crashing in the HV or Dom0 is kinda irrelevant. We have no Dom0 kernel in Fedora with which to debug / diagnose this problem. If you can identify an upstream changeset which fixes it by all means let us know & we'll patch the hypervisor with it, but aside fro mthat we're not putting any work into BZ reports against the HV / Dom0 until we have a working pv_ops DOm0 kernel present in Fedora again. (In reply to comment #3) > I am reopening this as I don't see that it's related to 437930. > > This is xen, not the Linux kernel. It's not getting to the kernel. What makes you think that? (XEN) traps.c:1838:d0 Attempt to change unmodifiable CR0 flags. (XEN) traps.c:413:d0 Unhandled general protection fault fault/trap [#13] on VCPU 0 [ec=0000] That suggests the linux Dom0 guest is trying to illegally modify CR0 and crashing. Until recently it used to get to "Xen is relinquishing VGA console" before crashing so something has changed here, but since we're know it's going to crash at *some* point, it's not worth debugging further. > This is F9 no more. 437930 is supposed to be fixed RSN and before F10. No progress has been made upstream, so we're not going to have Dom0 support in F10. See e.g.: https://www.redhat.com/archives/fedora-xen/2008-July/msg00048.html *** This bug has been marked as a duplicate of bug 437930 *** (In reply to comment #5) > > (XEN) traps.c:1838:d0 Attempt to change unmodifiable CR0 flags. > (XEN) traps.c:413:d0 Unhandled general protection fault fault/trap [#13] on > VCPU > 0 [ec=0000] > > That suggests the linux Dom0 guest is trying to illegally modify CR0 and > crashing. > > Until recently it used to get to "Xen is relinquishing VGA console" before > crashing so something has changed here, but since we're know it's going to > crash at *some* point, it's not worth debugging further. Oh, and incidentally - it's not a recent HV change, it's a recent kernel change. I tried an older HV and Dom0 crashes at the same point (In reply to comment #5) > (In reply to comment #3) > > I am reopening this as I don't see that it's related to 437930. > > > > This is xen, not the Linux kernel. It's not getting to the kernel. > > What makes you think that? > > (XEN) traps.c:1838:d0 Attempt to change unmodifiable CR0 flags. > (XEN) traps.c:413:d0 Unhandled general protection fault fault/trap [#13] on > VCPU > 0 [ec=0000] > > That suggests the linux Dom0 guest is trying to illegally modify CR0 and > crashing. > > Until recently it used to get to "Xen is relinquishing VGA console" before > crashing so something has changed here, but since we're know it's going to > crash at *some* point, it's not worth debugging further. > > > This is F9 no more. 437930 is supposed to be fixed RSN and before F10. > > No progress has been made upstream, so we're not going to have Dom0 support in > F10. See e.g.: > > https://www.redhat.com/archives/fedora-xen/2008-July/msg00048.html > > *** This bug has been marked as a duplicate of 437930 *** My interpretation is that XEN is trying to modify CR0. However, I don't know the code (and don't really want to). If fixing the other does not fix this, then _this_ report is likely to be overlooked. Certainly, there's not much information in the other duplicates to say they are the same as this. same behaviour in RHEL 5.3 beta. RHEL5.3 non Xen kernel now works on dc7700 (open since dec 2006), but the RHEL 5.3 / XEN option still crashes the system. Badly designed HP Enterprise desktop hardware that gets you every time. see: https://bugzilla.redhat.com/show_bug.cgi?id=218884 This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 to the applicable version. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. |