Description of problem: I tried to hibernate two qemu-kvm guests. One is running Fedora 24 KDE, and the other Fedora 24 Xfce. Kernel does not perform a hibernation. Instead, the system is cleanly powered off. Version-Release number of selected component (if applicable): kernel-4.5.0-302.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1.Boot an installed Fedora 24 system. 2.Log In to KDE. 3.Application launcher -> Leave -> Hibernate Actual results: 1. The system shuts down. Expected results: 1. The system should be hibernated. Additional info: I'll ping the QA ML in order to see if it's reproducible on bare metal.
Proposed as a Blocker and Freeze Exception for 24-beta by Fedora user juliuxpigface using the blocker tracking app because: Technically speaking, even if confirmed on bare metal, this might not strictly be a blocker, as the relevant criterion (2.6.6 Shutdown, reboot, logout) does not include "hibernation", but only "shutdown, reboot, logout". However, IF AND ONLY IF it'll be confirmed on bare metal, I think it's worth discussing it because it's an evident misbehavior. "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops. ". References: https://fedoraproject.org/wiki/Fedora_24_Beta_Release_Criteria#Shutdown.2C_reboot.2C_logout
Discussed at 2016-04-04 blocker review meeting: [1]. This bug was rejected as Beta blocker: the criteria do not cover hibernation and this is intentional, it's not considered release-blocking functionality (due to the difficulty of making it work reliably). it's also not really supported in VMs anyhow. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-04-04/f24-blocker-review.2016-04-04-16.05.html
Discussed at today's blocker review meeting [1]. Voted as RejectedFreezeException (Beta) - there does not appear to be any agreement even on who should be fixing what here, which makes it hard to grant this an FE. we would re-consider it if some specific development team would at least accept responsibility so it's clear roughly what will be fixed and how. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-04-18 Please see bug 1206936, this might be a duplicate of that one.
Just to be clear are you sure it's just cleanly powering off and not hibernating, but then not seeing the swap to resume from? If you haven't manually added resume= to your kernel arguments then it's presently not possible to hibernate and resume in Fedora. See this bug: BZ#1206936
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
This is mostly likely a dupe of bug 1206936. *** This bug has been marked as a duplicate of bug 1206936 ***