linux guest os does not recover from host sleep - Win 10 host

[eyn]

Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min.

If I send the host OS to sleep and immediately (within 5 min), everything is fine.

After a longer sleep, say 20 min, I get varying results:

1) the guest OS seems to have rebooted and I arrive at the login window. My prior running apps and consoles are gone from the desktop.

2) the OS hangs, showing the login screen. Mouse and keyboard are not working. Software reboot (send a shutdown signal) does not work. Must reboot the guest os.

My computer is recovering from sleep mode and not hibernate mode.

This seems to have started since 16.x. I created the guest OS in 15.x.

[eyn]

To clarify, I'm not sure how long sleep is engaged. It usually happens when I've left my computer for some period of time and the computer goes to sleep on its own. The problem doesn't seem to happen if I manually put the computer to sleep.

[eyn]

These were the last dying moments, 30 min before I attempted to wake it up. I started a terminal at 10:37 and then left for a while. Why does the guest session start having problems after a period of non-use?

11:35:18 systemd: Received SIGRTMIN+24 from PID 20848 (kill).
11:35:18 dbus-daemon: gnome-shell-calendar-server[18322]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
11:35:18 gvfsd: A connection to the bus can't be made
11:35:18 systemd: Stopping Evolution source registry...
11:35:13 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
11:35:13 gnome-shell: Failed to create backend: Unable to open display ':0'
11:35:13 gnome-session-b: gnome-session-binary[18051]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
11:35:13 gsd-color: Cannot open display:
11:35:13 gnome-session-b: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
11:35:13 gsd-wacom: Cannot open display:
11:35:13 gnome-session-b: gnome-session-binary[18051]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
11:35:13 gsd-clipboard: Cannot open display:
11:35:12 gnome-session-b: gnome-session-binary[18051]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
11:35:12 gsd-keyboard: Cannot open display:
11:35:12 systemd: gnome-terminal-server.service: Failed with result 'exit-code'.
11:35:12 gnome-session-b: gnome-session-binary[18051]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
11:35:11 gnome-shell: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gnome-session-b: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
11:35:11 at-spi-bus-laun:       after 333 requests (333 known processed) with 0 events remaining.
11:35:11 gsd-power: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gsd-xsettings: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gsd-wacom: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gsd-clipboard: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gsd-keyboard: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 kerneloops-appl: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
11:35:11 gsd-color: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gsd-media-keys: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 nautilus-deskto: nautilus-desktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 update-notifier: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 update-manager: update-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gnome-terminal-: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

11:35:11 gdm-x-session: (EE) Server terminated with error (1). Closing log file.
11:01:22 gnome-shell: g_array_unref: assertion 'array' failed
11:01:22 gdm-x-session: (EE) systemd-logind: failed to release device: Device not taken
10:41:59 pulseaudio: [alsa-sink-Intel ICH] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
10:37:46 systemd: Started GNOME Terminal Server.
10:37:46 dbus-daemon: [session uid=1001 pid=18047] Successfully activated service 'org.gnome.Terminal'
10:37:45 systemd: Starting GNOME Terminal Server...

[Socratis]

Replying to eyn:

Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min.

So, if you downgrade to 5.2.x, the issue goes away?

My computer is recovering from sleep mode and not hibernate mode.

How do you know? What are the Power Settings on your Host? And I mean the details, not the SchemeName. Are you sure your computer doesn't go into "deep sleep"? Which has definitely its own share of issues (search the webs), even on real, physical systems?

This seems to have started since 16.x. I created the guest OS in 15.x.

15.x and 16.x versions of what? Maybe you mean VirtualBox 5.x and 6.x?

Why does the guest session start having problems after a period of non-use?

Because the Host is pulling the rug under the Guest's feet. Without the Guest's knowledge, all of a sudden the CPU (for example) goes AWOL. And the Guest is left to figure out (with not too much luck most of the time) what exactly happened. Not an easy problem to solve...

You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

[Kris Thielemans]

(similar to https://www.virtualbox.org/ticket/19716, but for me this happens with a single monitor)

I see the same, or at least it sounds very similar. For me it happens every time the host goes to Sleep.

• Host: fully-update Windows 10 Pro, brand new HP laptop
• VB: 6.1.14
• Guest: Ubuntu 18.04 (VM exported from previous laptop running VB 6.0.x (sorry, can't check anymore), and imported in new VBox, VGA updated)

As noted by the OP, the VM is actually alive. The clock on the login-screen keeps running. The VBox log contains the heartbeat. However, it doesn't respond to keyboard (but physical and soft) nor mouse input. The only way out for me is a hard-reset of the VM. For instance, in the attached log, hte VM hung after a sleep (log time stamp 06:33 i guess), I've tried to suspend it (works fine), start it again (works fine, but is in same state), resize its window (works fine), use the VB menu to send a Shutdown signal (doesn't do anything), then reset.

I've attached a file with some info from powercfg on sleep settings.

Otherwise, everything seems to be working fine (i.e. as long as the laptop doesn't sleep).

[Kris Thielemans]

powercfg output krthie

[Kris Thielemans]

VBox log krthie (including attempted shutdown)

[Kris Thielemans]

confirmed that this is a guest GUI problem: I've enabled ssh access to my Ubuntu VM. When the guest "hangs", I can then ssh into it, and do sudo service gdm restart. Everything's back to working then (of course, I've killed all my existing terminals etc). Maybe someone can tell me where to find gdm log files which might help.

Note that I've tried this now with VB 6.1.16 and 6.0.24. All have the same problem

[dimasamodurov]

I have the same issue with Win 10 host, VBox 6.1.16 and Ubuntu 20.04.1 guest. If i close and open the laptop, the guest OS becomes inaccessible.

[Laurentzed]

I have a similar issue with:

Host Windows 10 Pro Guest Ubuntu 20.04.5 LTS

When the host resumes from a 10 minutes suspend, the guest is unresponsive.

Here is the VBox log concerning it:

---

09:16:05.573017 Audio: Output channels = 0 11:08:31.117591 TM: Giving up catch-up attempt at a 3 143 813 806 768 ns lag; new total: 6 737 593 843 938 ns 11:08:31.117674 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 3144 seconds ago 11:08:31.117917 VMMDev: GuestHeartBeat: Guest is alive (gone 3 144 127 668 643 ns) 11:08:31.220839 TMR3UtcNow: nsNow=1 663 228 299 254 406 769 nsPrev=1 663 225 154 816 190 974 -> cNsDelta=3 144 438 215 795 (offLag=438 831 offVirtualSync=6 737 594 282 769 offVirtualSyncGivenUp=6 737 593 843 938, NowAgain=1 663 228 299 254 845 600) 11:08:31.220916 VMMDev: Guest Log: 07:51:39.260304 timesync vgsvcTimeSyncWorker: Radical guest time change: 3 144 434 644 000ns (GuestNow=1 663 228 299 260 288 000 ns GuestLast=1 663 225 154 825 644 000 ns fSetTimeLastLoop=false) 11:08:32.002586 NAT: DHCP offered IP address 10.0.2.15 11:08:32.273927 Audio: Device configuration of driver 'WasAPI' has changed 11:08:32.736779 Audio: Found 5 devices for driver 'WasAPI' 11:08:32.736819 Audio: Device 'Enceintes (Realtek(R) Audio)': 11:08:32.736820 Audio: ID = {0.0.0.00000000}.{aa4b993d-7f09-4666-866c-87c3b9d8777b} 11:08:32.736821 Audio: Usage = output 11:08:32.736821 Audio: Flags = DEFAULT_OUT 11:08:32.736822 Audio: Input channels = 0 11:08:32.736822 Audio: Output channels = 2 11:08:32.736827 Audio: Device 'LG HDR 4K (HD Audio Driver for Display Audio)': 11:08:32.736827 Audio: ID = {0.0.0.00000000}.{21eee21f-2f0d-4641-82fb-e8004c722255} 11:08:32.736828 Audio: Usage = output 11:08:32.736828 Audio: Flags = NONE 11:08:32.736828 Audio: Input channels = 0 11:08:32.736829 Audio: Output channels = 2 11:08:32.736833 Audio: Device 'Enceintes (Realtek(R) Audio)': 11:08:32.736833 Audio: ID = {0.0.0.00000000}.{aa4b993d-7f09-4666-866c-87c3b9d8777b} 11:08:32.736834 Audio: Usage = output 11:08:32.736834 Audio: Flags = NONE 11:08:32.736834 Audio: Input channels = 0 11:08:32.736835 Audio: Output channels = 2 11:08:32.736838 Audio: Device 'Réseau de microphones (Intel® Smart Sound Technology for Digital Microphones)': 11:08:32.736838 Audio: ID = {0.0.1.00000000}.{371c912f-d78f-47e9-9364-86f1431e6cae} 11:08:32.736839 Audio: Usage = input 11:08:32.736839 Audio: Flags = DEFAULT_IN 11:08:32.736839 Audio: Input channels = 4 11:08:32.736840 Audio: Output channels = 0 11:08:32.736843 Audio: Device 'Réseau de microphones (Intel® Smart Sound Technology for Digital Microphones)': 11:08:32.736844 Audio: ID = {0.0.1.00000000}.{371c912f-d78f-47e9-9364-86f1431e6cae} 11:08:32.736844 Audio: Usage = input 11:08:32.736844 Audio: Flags = NONE 11:08:32.736844 Audio: Input channels = 4 11:08:32.736845 Audio: Output channels = 0 11:08:35.117932 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago 11:09:09.614890 VMMDev: GuestHeartBeat: Guest is alive (gone 38 496 970 993 ns)

Any idea?