Bug 436249
| Summary: | (XEN) Domain 0 crashed: rebooting machine in 5 seconds. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Summerfield <debian> |
| Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | Keywords: | Reopened |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-14 18:26:27 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-03-06 03:26:54 UTC
To disable the automatic reboot, just add 'noreboot' to the hypervisor boot command line args in grub. Five seconds is way too fast. There needs to be enough time for a user to realise something is wrong and read the messages. The current delay is barely enough time to photograph the screen (I had to do that recently for another bug). The default operation should be the same as Linux kernels, much as I dislike hard lockups. Best default for both, I think, would be to await control-alt-del. btw Where are the xen options documented? Certainly not in the package. THis needs to be against kernel-xen, since that's where the hypervisor lives. I'm still not inclined to chance the default Xen hypervisor reboot behaviour, but will leave it up kernel guys to decide. I wonder whether this should be reassinged to alanc, the original problem is a manifestation of 436099 on the same hardware, and which it is (properly) assigned to him. 436099 is closed, the original problem (probably) needs the same fixed. Possibly to should also have been marked f9-kernel-blocker, as the other was. Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. |