Hide Forgot
Created attachment 488041 [details] In Xen, don't try to stop other CPUs on reboot or shutdown Description of problem: The last one or two F13 kernels, when running as a paravirtualized guest under Xen with more than one virtual CPU, cannot be rebooted or completely shut down properly. They will go through the entire shutdown process, but when the actual restart should happen (or in the case of a shutdown, when the domain should cease to exist), the domain simply hangs, and it requires administrator intervention on the dom0 to 'xm destroy' and then 'xm create' the F13 guest again. This used to work just fine. Version-Release number of selected component (if applicable): 2.6.34.8-68.fc13.x86_64 How reproducible: 100% Steps to Reproduce: 1. Set up an F13 Xen guest VM with multiple vcpus, update it to the current kernel, set up a serial console, boot it as a paravm. 2. Log in on the guest's console and run 'reboot'. 3. Note that at the end of the shutdown process, the guest appears to hang. Notice that on the dom0, 'xm list' output for the relevant guest domain indicates that it now has 1 vcpu. Additional info: This issue is XenSource bug 1695: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1695 As described in that bug, the patch is trivial, and it is in the upstream kernel in 2.6.35.10. The upstream diff is here: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=31e323cca9d5c8afd372976c35a5d46192f540d1 I've also attached the upstream patch for convenience. Since that commit is present in 2.6.35.10, I believe this bug should not affect Fedora 14 or later, though I have not explicitly checked that. I have rebuilt the 2.6.34.8-68.fc13.x86_64 kernel with this patch and verified that it corrects the problem. This is a serious issue for production VMs that either automatically reboot on a periodic basis or whose sysadmins do not have control of the dom0, so it would be great if this patch could be incorporated into the F13 kernel as soon as practical.
Over two weeks have gone by since this bug with a provided simple fix was opened without any response, and no changes have been made to the F13 branch in git. This bug continues to cause problems on production systems. Would it be possible to get some feedback on when this will be fixed?
Patch is in 2.6.34.9
kernel-2.6.34.9-69.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/kernel-2.6.34.9-69.fc13
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
kernel-2.6.34.9-69.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.