virtualbox.org

Running Vbox Version 6.1.30 r148432 (Qt5.6.2)
Windows 10 host running 8 core Intel I7 CPU with 64 GB of RAM
Ubuntu 20 64bit guest running 4 CPU with 32 GB of RAM
Since upgrading my guest to Ubuntu 20 the Guest frequently crashes when the host goes to sleep.

In reviewing the log from the most recent crash, I found the following exception:
04:11:19.806407 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000000cb4!!!

Hyper V is disabled on the Host.
I have tried disabling audio on the guest per other suggestions on the forum. No luck.

Log file from the most recent crash attached. Additional but seemingly related issue.
Frequently, this VM will also hang when the host goes to sleep.
Please refer to the attached log file for details. More Information...
I can run this VM successfully on an older laptop.
In reviewing the logs from this laptop, I noticed, in the attached log, that when the host goes to sleep, VirtualBox explicitly pauses the VM due to a host suspend per the following log entry:

01:35:17.733512 Pausing VM execution, reason 'host suspend'

Nowhere in the logs for my new laptop do I see this action take place.
Any thoughts on why VirtualBox on my new laptop is not handling the host suspend event?
Here is the log from my old laptop that can run the VM successfully. Thanks in advance for your help.

The crash inside the lxGaryDev-2021-12-30-21-48-26.log file is rather in the graphics department (than in audio).

I'd suggest to set the Video Memory to 128 MB, and install the VirtualBox Guest Additions 6.1.30 (instead of 6.0.18) inside the guest OS. Does the crash still occur then?

I updated to the latest Guest Additions and increased the video memory to 128MB.
Now I can't enable the second monitor.

Ok.
I had to install Guest Additions 6.1.30 twice.
I was then able to get my second monitor to work.
I also increased the video memory to 128MB.
Unfortunately, my VM still hung when the host went to sleep.
In reviewing the attached log, I still see that the "Pausing VM execution, reason 'host suspend'" notification and subsequent Guest suspension notifications that were present on my old laptop, still do not show up on my new laptop.

You could perhaps investigate which sleep mode the two hosts go into ...

What do you mean "which sleep mode the two hosts go into"?
They are both running Windows 10 and there appears to be only one sleep mode.
Is there something specific I should be looking for?

You're right in that my question wasn't technically correct.

When you wrote "host went to sleep", this could mean a lot of different things (e.g. Sleep, Hibernate, Fast Startup), and especially the Sleep mode could be configured to only use screen blanking and keeping the CPU awake. Additionally, there are several possibilities how to "go to sleep" (e.g. timeout, closing the lid of a notebook/laptop, terminal commands).

Tip: If you don't like to click through the Windows dialogs to compare the power management settings, you can query the complete settings of the current power saving mode with powercfg /q in a command prompt.

Thanks for the clarification.
I configured turning off the screen and sleep settings in the Windows Power and Sleep settings under System Settings.
The settings are identical on both laptops.
Recognizing that I updated the VM with the latest Guest Additions and increased the Video Memory to 128MB, I copied the VM from the new laptop to my old laptop to ensure I was using the same VM on both.
I tested my old laptop again, and again found that my old laptop was handling the host sleep while the new one was not.
Here is an extract from the log on my old laptop:

00:04:25.410050 Pausing VM execution, reason 'host suspend'
00:04:25.410142 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:04:25.418843 AIOMgr: Endpoint for file 'D:\Data\Development\VirtualBox VMs\lxGaryDev\lxGaryDev.vdi' (flags 000c0781) created successfully
00:04:25.462701 PDMR3Suspend: 52 515 766 ns run time
00:04:25.462721 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:04:25.462737 Console: Machine state changed to 'Paused'
00:04:25.462928 GUI: Releasing keyboard on pause/stuck
00:04:25.462956 GUI: Releasing mouse on pause/stuck
00:09:19.117396 Resuming VM execution, reason 'host resume'
00:09:19.117504 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:09:19.117913 AIOMgr: Endpoint for file 'D:\Data\Development\VirtualBox VMs\lxGaryDev\lxGaryDev.vdi' (flags 000c0723) created successfully
00:09:19.125400 Changing the VM state from 'RESUMING' to 'RUNNING'
00:09:19.125429 Console: Machine state changed to 'Running'

Nowhere in the logs on my new laptop, do I see VirtualBox handling the host suspend as shown above.
I have attached the latest log from my old laptop for your reference. This appears to be a bit of a "smoking gun".
Any clue why my new laptop would not be handling the host sleep event while my old one clearly does?

Thanks,
Gary

When doing further tests, please note down wall clock times for relevant actions (VM start, VM window (de-)activation [mouse clicks inside/outside the VM window], host going to sleep), to make it easier to align your actions with the log files, especially when there are no log messages created.

What happens when you try to pause and unpause the VM using the VM window's menu (Machine > Pause)?

Does it make a difference if you're using only the laptop display?

Does it make a difference if the VM is in normal (windowed) mode instead of full-screen mode?

On both Windows hosts, check the events in the Windows Event Viewer. Does it make a difference how you trigger the host event to go to sleep?