Description of problem: Shutdown of windows server 2003 x64 from inside the server or from virt-manager icon does not poweroff the guest. Restarting the guest from the guest (windows start menu) doest not work either. It seems the power-recykling and poweroff message from guest to the bios/kvm is not recevied/accepted or correctly handled. It is possibel to force-power-off the guest from the virt-manager icon og using virsh destroy. Version-Release number of selected component (if applicable): kvm-74-10.fc10.x86_64 How reproducible: Shutdown of windows server 2003 x64 from inside the server or from virt-manager icon does not poweroff the guest. The guest "shuts everything down" except the "power". Steps to Reproduce: 1. 2. 3. Actual results: there is a zombie guest taking full guest-cpu-time. Expected results: the system guest system is fully shutdown. Additional info:
win2003x64vl.xml: <domain type='kvm'> <name>win2003x64vl</name> <uuid>602fe93e-e4dc-b889-efab-bc11eedf5887</uuid> <memory>1572864</memory> <currentMemory>1572864</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <source file='/vm_store/win2003x64vl/win2003x64vl.img'/> <target dev='hda' bus='ide'/> </disk> <disk type='file' device='cdrom'> <target dev='hdc' bus='ide'/> <readonly/> </disk> <interface type='bridge'> <mac address='54:52:00:26:03:24'/> <source bridge='switch'/> </interface> <serial type='pty'> <source path='/dev/pts/6'/> <target port='0'/> </serial> <console type='pty' tty='/dev/pts/6'> <source path='/dev/pts/6'/> <target port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='da'/> </devices> </domain>
I have also tested windows xp 32bit version. The acpi is disabled by default. It will not poweroff when shutdown inside guest. It powers off when I use the poweroff button from virt-manager. Tried to enable acpi, but that does not help at all.
Here's a similar report on the kvm@vger list: http://www.mail-archive.com/kvm@vger.kernel.org/msg08252.html Manmathan: is there any chance you could try and reproduce with the F11 Beta coming out soon (or rawhide)?
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.