Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Reboot and Shut Down item in Virtual Machine menu don't work|
|Product:||[Fedora] Fedora||Reporter:||Honza Horak <hhorak>|
|Component:||gnome-power-manager||Assignee:||Richard Hughes <richard>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||15||CC:||berrange, crobinso, hbrock, jforbes, richard, virt-maint|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-08-07 16:02:47 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Honza Horak 2011-04-28 09:29:27 EDT
Description of problem: I have F15 installed in my VM and VM itself is running on F15, too. When I press either Reboot or Shut Down items from main menu in Virtual Machine, screen gets black (text mode) with only text cursor displayed for some time (approx. 1 to 3 minutes) and then come back to gnome without rebooting/shutting down. Version-Release number of selected component (if applicable): rpm -q virt-manager virt-manager-0.8.7-4.fc15.noarch How reproducible: everytime Steps to Reproduce: 1. run F15 in VM 2. press Reboot or Shut Down item in main menu 3. wait and see what is done Actual results: Screen switches to text mode for some time and then returns back Expected results: VM should restart/shut down Additional info: Force off is the only way to kill running VM from outside, this works well.
Comment 1 Honza Horak 2011-04-28 10:33:29 EDT
It seems working well when RHEL-5 is running in VM, so maybe it is not problem in VM.
Comment 2 Cole Robinson 2011-04-28 11:58:56 EDT
What about doing 'shutdown -h now' on the command line from inside the VM? Or using gnome UI to shutdown? If that doesn't work, please reassign to systemd or gnome-power-manager
Comment 3 Honza Horak 2011-04-29 02:53:14 EDT
When I run "shutdown -h now", system in VM shuts down correctly, but VM doesn't recognize this (it still offers Restart, Shut Down and Force off, but not Run in the main menu, even if the system is running no more). Then if I try to Force it off again, error is printed: "Error shutting down domain: Requested operation is not valid: domain is not running" and the following trace is in details: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 911, in _do_destroy_domain vm.destroy() File "/usr/share/virt-manager/virtManager/domain.py", line 1168, in destroy self._backend.destroy() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 346, in destroy if ret == -1: raise libvirtError ('virDomainDestroy() failed', dom=self) libvirtError: Requested operation is not valid: domain is not running After that VM is correctly off again and I can press Run. However, this is not happening every-time, "shutdown -h now" command sometimes works as expected, system shuts down and is able to run again without problems. I haven't found the case when it behaves incorrectly yet, maybe when VM is running for a longer time. So I'm still not sure where the problem is, while there are some known problems with suspending F15 (which is not running in VM, see bug #698135), so feel free to reassign this. Note: pressing Reboot or Shut down from VM's main menu fails every-time.
Comment 4 Cole Robinson 2011-04-29 10:35:09 EDT
Jan, if you can reproduce that issue with virt-manager getting out of sync, please file a separate virt-manager bug, and include the relevant output of ~/.virt-manager/virt-manager.log For the original issue, if the virt-manager shutdown button is triggering _any_ behavior change in the guest, virt-manager/libvirt are at least doing their job. So my guess is that whatever is handling the acpi shutdown signal isn't doing it's job? Reassigning to gnome-power-manager for now
Comment 5 Eric Blake 2011-09-26 14:21:46 EDT
See also bug 741375 against F16, where the default acpi behavior for an F16 guest still prevents host-initiated clean shutdown.
Comment 6 Fedora End Of Life 2012-08-07 16:02:52 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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