Bug 192044
Summary: | Under xen, shutdown -h in dom0 does not shut down machine. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Reish <dreish> |
Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | bstein |
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: | 2008-02-26 23:07:40 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
Dan Reish
2006-05-17 00:19:34 UTC
Can you confirm if this fails with 2.6.16-1.2118 kernel-xen0 and correctly works with 2054 kernel-xen0? Or if this behavior also happens on the standard non-xen 2111 kernel? Shutting down works under kernel-2.6.15-1.2054_FC5. Unfortunately, I can't boot Xen anymore because I have moved my drives under an Areca RAID controller, and the arcmsr.ko I have does not work with any kernel-xen0, so I can't try 2054 kernel-xen0, but I confirmed a few times (involuntarily) that it failed with 2.6.16-1.2118 kernel-xen0. The motherboard on this machine is an Intel D955-XBK, which apparently has some bugs. The Areca card does not function with that motherboard when exactly 2 gb of RAM is installed. More or less RAM is fine. Areca tech support claims this problem only exists with this and another Intel MB. Still, if regular Linux can shut down successfully, I would think it ought to be possible for Xen. Does this fail with the 2.6.16-1.2118 (non-xen) kernel? change QA contact This report targets FC5, which is now end-of-life. Please re-test against Fedora 7 or later, and if the issue persists, open a new bug. Thanks |