Keep the guest out of S3 and S4 sleep states - #79
Merged
Merged
Conversation
Choosing Suspend in Omarchy's power menu put the VM into QEMU's suspended state: the window froze and nothing from the keyboard brought it back. With S3 and S4 disabled on the q35 ICH9 the guest cannot enter that state; a suspend request falls through to suspend-to-idle, which keeps QEMU running and wakes on input. Verified in the VM: QEMU stays running through systemctl suspend where it previously reported suspended.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found during the post-release sweep. Choosing Suspend in Omarchy's power menu (or
systemctl suspend) put the VM into QEMU'ssuspendedstate: the window froze, QMP still answered so the launcher's watchdog saw nothing wrong, and no keyboard input brought the guest back. Only asystem_wakeupover QMP did.With
-global ICH9-LPC.disable_s3=1anddisable_s4=1the guest cannot enter those states. A suspend request now falls through to suspend-to-idle, which keeps QEMU running and wakes on input; Omarchy's sleep lock still engages, so the user sees the lock screen rather than a dead window. Verified in the Win11 VM:systemctl suspendleft QEMU reportingrunning, where the same command before this change reportedsuspended.Seeding Omarchy's
suspend-offtoggle for new VM users, so the menu does not offer Suspend at all, follows as a guest patch.