In Virtual Machine Manager, the VM gets blacked out and it is written “Display output is not active.”
I tried to activate the screen by moving the mouse, ESC key and
Several keystrokes with the menu above. I had to force switching off.
The Automatic Suspend is On, switching it off would not block the screen and no “Force off” would be needed.
This is by design – at least, when installing not on a virtual machine. For one thing, it’s necessary in order to get the power-consumption scores to acceptable levels to sell in some markets. I think it’s also the right thing to do by default — idle devices use more power than they need to.
Arguably a VM is a special case. But I don’t think that falls under Common Issues, but rather a suggestion for the Workstation Working Group.
There appears to be something wonky with suspend on F38. I haven’t been able to wake my machine from suspend either.
ATM I just have suspend disabled. I’ll file a report as soon as I figure out how to get the report uploader to work :P.
First, we’ll likely publish this in Common Issues even though it’s not a bug (it’s an intentional change), because this is very high-profile and many people will likely consider it a bug.
Second, if anyone shows me how to reproduce this issue in a VM (including that it can’t be resumed), I’ll propose it as a blocker bug. In all my testing, my VMs simply ignored the automatic suspend timeout and never suspended.
As I understood reading all the additional information Kamil posted is, that the sequence in a virtualization, how to deal with a suspend was wrong.
Instead of Gnome checking if in a VM before initiate a suspend it just suspended the guest what killed it.
Changing the sequence to, if Gnome is a vm don’t suspend, let’s the guest alive. Suspension just should be possible from the Host, right?