Bug 739982
Summary: | Xen Dom0 hangs on reboot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bogdan B <bodkos> |
Component: | xen | Assignee: | Michael Young <m.a.young> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | berrange, bodkos, jforbes, kraxel, m.a.young, myroslav, virt-maint, xen-maint |
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: | 2012-08-07 21:29:12 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
Bogdan B
2011-09-20 15:37:24 UTC
The system will shut down if you wait long enough (several minutes). The problem is that the xen and libvirt (if you have it installed) processes need to be shut down in the right order, for example xenstored needs to be running to allow both xenconsoled and libvirt-guests to be shut down, though I think there are further dependencies. Currently systemd doesn't know about these dependencies, so doesn't shut down the processes down in the right order, and therefore hangs at various stages until each times out. You can fix the xenstored/xenconsoled dependency by editing /etc/rc.d/init.d/xenconsoled and replacing the line # Required-Stop: $syslog $remote_fs with # Required-Stop: $syslog $remote_fs xenstored Though it didn't work for me the exact way you mentioned (system still didn't reboot properly with xenstored in Required-Stop list). But I've found that using xencommons instead of xenstored/xenconsoled solved the issue. So the proper way to fix this in my case was: chkconfig --add xencommnos (btw this service isn't initially in chkconfig) chkconfig xenconsoled off chkconfig xenstored off Though it didn't work for me the exact way you mentioned (system still didn't reboot properly with xenstored in Required-Stop list). But I've found that using xencommons instead of xenstored/xenconsoled solved the issue. So the proper way to fix this in my case was: chkconfig --add xencommnos (btw this service isn't initially in chkconfig) chkconfig xenconsoled off chkconfig xenstored off I hope this has been fixed from xen-4.1.1-6 and onwards (without enabling the xencommons script). Are you still seeing the problem? This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. |