Hide Forgot
Description of problem: if I create a HVM Windows VM and then issue an "xl shutdown VM" the machine remains in ---s-- state, even if I leave the default behavior or configure it as on_poweroff = 'destroy'. Also happens in reboot, with ---sr- state. Even the last XEN package has this behaviour. I tried "old" signed windows xen PV driver, and also the latest git. Version-Release number of selected component (if applicable): xen-4.5.3-9.fc23.x86_64 (but also the previous I installed, xen-4.5.3-6.fc23.x86_64 if I remember correctly) How reproducible: create an HVM machine, then issue an xl shutdown VMNAME. Steps to Reproduce: 1. xl create VMNAME.conf 2. wait to boot up correctly 3. xl shutdown VMNAME 4. VMNAME shuts down correctly, DOMU is aware of shutdown Actual results: xl list shows VMNAME in ---s-- state forever Expected results: no VMNAME in xl list, HVM destroyed as configured Additional info: I have a 2 node DRBD master-master with pacemaker. Pacemaker hides this, because agent destroys VM. The cluster runs from F22 without problems, this happens with no configuration changes, just dnf upgrade.
Some other (unuseful) logs: [root@dom0 ~]# tail /var/log/xen/qemu-dm-hvm.log ACPI:debug: write addr=0xb044, val=0xfc. ACPI:debug: write addr=0xb045, val=0x89. ACPI:debug: write addr=0xb044, val=0xfd. ACPI:debug: write addr=0xb045, val=0x89. ACPI:debug: write addr=0xb044, val=0xfe. ACPI:debug: write addr=0xb045, val=0x89. ACPI:debug: write addr=0xb044, val=0xff. ACPI:debug: write addr=0xb045, val=0x89. reset requested in cpu_handle_ioreq. Issued domain 32 reboot [root@dom0 ~]# tail /var/log/xen/xl-hvm.log Waiting for domain hvm (domid 32) to die [pid 12044] [root@dom0 ~]# xl list (snipped) hvm 32 12287 1 ---sr- 44730.4
I can confirm the bug is there: I updated the cluster to F24 (see bug 1370095) so I am now on Xen 4.6.3 and kernel 4.7.6, everything is working as espected again.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.