Linux guest GUI freeze or full VM hang after not being interracted with for some time

[Fieldy]

Linux guest GUI freeze or full VM hang after not being interacted with for some time

Terms in use:

• GUI Freeze: The GUI inside the VM, XFCE, is not responsive. The VM is still active, as can be seen by the activity indicators (disk, network, etc). A console can be brought up (ctl-alt-F2 for example), logged into, and all of my users processes killed with "pkill -u myusername". This causes the GUI to become responsive, giving me the fresh login screen. This is not optimal, however, at least it's a clean shutdown of programs. Alternately I can perform an ACPI shutdown and the system will shut down cleanly.

• Full VM Hang: The GUI inside the VM, XFCE, is not responsive. The VM is NOT active, as the activity indicators are inactive. A console can NOT be brought up (ctl-alt-F2 for example). Using the soft keyboard and trying the same has no effect. Sending ACPI shutdown signals has no effect. At the same time as this, sometimes the virtualbox GUI for managing the virtual machines hangs. This can only be resolved by manually killing off the VM and anything virtualbox related, and rebooting the host.

VirtualBox information:

• Version 6.1.16
• Extension pack 6.1.16

Host information:

• Windows 10 pro
• Intel 4GHz corex CPU
• 128GB RAM
• Samsung SSD Disks
• Nvidia GeForce RTX 2080 Ti using Nvidias drivers

Guest information:

• Linux Mint 20
• GUI: XFCE
• Guest additions: 6.1.16
• Virtual RAM: 9240 MB
• Virtual processors: 6
• Acceleration: default
• Display: 128MB RAM, VMSVGA, Enable 3D Acceleration
• Storage: SATA: Disk 1: Linux_Mint_19.vdi | Virtual size: 300GB | Actual size: 91GB
• Storage: SATA: Disk 2: Linux_Mint_19_swap.vdi | Virtual size: 16GB | Actual size: 9GB

===

Issue Details:

Frequently after being away at least 10 or 15 minutes the guest will either experience a GUI freeze (see above for a description), or a full VM hang. The first situation can be recovered from, however in the second situation nothing can be done. For this reason I take frequent snapshots while the VM is powered on so that I can use them to restore from as setting everything back up again and again and again gets frustrating.

===

Solutions attempted:

Disable the screen saver / screen lock etc inside of the guest: The prior night I did this and returned in the morning to find that a full VM hang had taken place shortly after I had left to go to sleep. I know when it took place because of the time shown in the GUI (stuck).

Restore the latest snapshot, cleanly shut down, and power the VM on again: The issue still frequently occurs.

Disable 3D Acceleration: The issue still frequently occurs.

===

Logs:

Note: For each of the logs, I prefix a string like "round1" and then refer to them that way. Please be sure to refer to them that way to me as well.

The last log in round1 Vbox.log for this VM is:

14:38:47.761976 GUI: UIMediumEnumerator: Medium-enumeration finished!

The full round1 Vbox.log will be attached. In addition I'll attach round1 VBox.log.1 , VBox.log.2 and VBox.log.3 .

round1 VBoxHardening.log doesn't really make sense to me so I'll just attach it.

Windows event log upon shutting down the host for round1, since it was both a full VM hang AND the virtualbox management interface became unresponsive:

{{{winlog.event_data.Caption:

VirtualBox: VirtualBox.exe - Application Error

message:

Application popup: VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program

agent.hostname:

MY-SYSTEM-NAME

agent.name:

MY-SYSTEM-NAME

agent.id:

130ce1c1-0e0a-419c-9b7f-f4bf70a6c377

agent.type:

winlogbeat

agent.ephemeral_id:

002ca6d2-1396-44b0-9a31-ec9b95be97bc

agent.version:

7.9.0

winlog.record_id:

2,049

winlog.computer_name:

MY-SYSTEM-NAME

winlog.process.pid:

16,852

winlog.process.thread.id:

2,196

winlog.event_id:

26

winlog.task: winlog.provider_guid:

{47bfa2b7-bd54-4fac-b70b-29021084ca8f}

winlog.channel:

System

winlog.event_data.Message:

The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program

winlog.api:

wineventlog

winlog.provider_name:

Application Popup

winlog.opcode:

Info

winlog.user.identifier:

S-1-5-18

winlog.user.domain:

NT AUTHORITY

winlog.user.name:

SYSTEM

winlog.user.type:

User}}}

===

Follow up:

What more can I provide to assist?

[Fieldy]

Round1 VBox.log

[Fieldy]

Round1 VBox.log.1

[Fieldy]

Round1 VBox.log.2

[Fieldy]

Round1 VBox.log.3

[Fieldy]

Round1 VBoxHardening.log (compressed as it was too large)

[Fieldy]

Round 2 - 20201116

Additional solution tried: I did turn off the guests screensaver and screen lock earlier. However, I then found that there are display power settings that were enabled that were separate. I turned that off yesterday.

Solution result: The VM was left on overnight, and I came back in the morning to find it operating as normal.

Unfortunately,...

Issue encountered: Later in the day I was away for roughly 20 minutes, and came back to a full VM hang. The virtualbox management interface was also unresponsive.

Logs:

Note: For each of the logs, I prefix a string like "round1" and then refer to them that way. Please be sure to refer to them that way to me as well.

Windows event logs: There are several of these at the time of the issue:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: VirtualBox.exe
P2: 6.1.16.40961
P3: 5f89bd81
P4: Qt5WidgetsVBox.dll
P5: 5.6.2.0
P6: 58e2628d
P7: c000041d
P8: 00000000002f84ae
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE21.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_VirtualBox.exe_77e6c6b822d27cece42bd8fb2a3085b7973aa7_a40808ac_d5bd5e17-3742-4189-b6a9-c64c1e79a7ae

Analysis symbol: 
Rechecking for solution: 0
Report Id: 598f24e5-35ed-4a3a-8dd1-3f83037d45a1
Report Status: 100
Hashed bucket: 
Cab Guid: 0

I could not find C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE21.tmp.WERInternalMetadata.xml however I did find C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_VirtualBox.exe_77e6c6b822d27cece42bd8fb2a3085b7973aa7_a40808ac_d5bd5e17-3742-4189-b6a9-c64c1e79a7ae\Report.wer:

Version=1
EventType=APPCRASH
EventTime=132498607923122624
ReportType=2
Consent=1
UploadTime=132500390023337851
ReportStatus=100
ReportIdentifier=d5bd5e17-3742-4189-b6a9-c64c1e79a7ae
IntegratorReportIdentifier=598f24e5-35ed-4a3a-8dd1-3f83037d45a1
Wow64Host=34404
NsAppName=VirtualBox.exe
OriginalFilename=VirtualBox.exe
AppSessionGuid=00000578-0002-000e-0981-7529c8bad601
TargetAppId=W:0006d84b5a36c8e2df46094d036e2f4fca5200000904!0000429c3517ce0fd69bcb66eb7f6cc498d7b5f50dfb!VirtualBox.exe
TargetAppVer=2020//10//16:15:34:25!252253!VirtualBox.exe
BootId=4294967295
ServiceSplit=572653752
TargetAsId=13303
UserImpactVector=3146544
IsFatal=1
EtwNonCollectReason=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=VirtualBox.exe
Sig[1].Name=Application Version
Sig[1].Value=6.1.16.40961
Sig[2].Name=Application Timestamp
Sig[2].Value=5f89bd81
Sig[3].Name=Fault Module Name
Sig[3].Value=Qt5WidgetsVBox.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=5.6.2.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58e2628d
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=00000000002f84ae
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=dd0a
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=dd0a88242ff3e5d666aac5c868ecc3cb
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=b379
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=b379bc0149e9aa7b2a41bd195b854bbd
UI[2]=C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
LoadedModule[0]=C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\USER32.dll
LoadedModule[5]=C:\WINDOWS\System32\win32u.dll
LoadedModule[6]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[7]=C:\Program Files\Oracle\VirtualBox\UICommon.dll
LoadedModule[8]=C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
LoadedModule[9]=C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[11]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[12]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[13]=C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
LoadedModule[14]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\sechost.dll
LoadedModule[17]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[18]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[19]=C:\WINDOWS\System32\ole32.dll
LoadedModule[20]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[21]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[22]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[23]=C:\WINDOWS\System32\combase.dll
LoadedModule[24]=C:\WINDOWS\System32\shcore.dll
LoadedModule[25]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[26]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[27]=C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
LoadedModule[28]=C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
LoadedModule[29]=C:\WINDOWS\System32\profapi.dll
LoadedModule[30]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[31]=C:\Program Files\Oracle\VirtualBox\Qt5PrintSupportVBox.dll
LoadedModule[32]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[33]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[34]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[35]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[36]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[37]=C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[41]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.1016_none_73b3274ad815f571\COMCTL32.dll
LoadedModule[42]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[47]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[49]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[50]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
LoadedModule[51]=C:\WINDOWS\System32\Wintrust.dll
LoadedModule[52]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[53]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[54]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[55]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[57]=C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
LoadedModule[58]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[59]=C:\WINDOWS\system32\userenv.dll
LoadedModule[60]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[61]=C:\Program Files\Oracle\VirtualBox\VBoxC.dll
LoadedModule[62]=C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
LoadedModule[63]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[65]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[66]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[67]=C:\WINDOWS\SYSTEM32\amsi.dll
LoadedModule[68]=C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2008.9-0\MpOav.dll
LoadedModule[69]=C:\WINDOWS\system32\version.dll
LoadedModule[70]=C:\WINDOWS\system32\dwrite.dll
LoadedModule[71]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[72]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[73]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[74]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[75]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[76]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[77]=C:\WINDOWS\system32\RMCLIENT.dll
LoadedModule[78]=C:\WINDOWS\System32\TextInputFramework.dll
LoadedModule[79]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[80]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[83]=C:\WINDOWS\System32\iertutil.dll
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=1016
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=97457
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.1016.18362.0-11.0.205
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=130769
OsInfo[19].Key=svolsz
OsInfo[19].Value=469
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.1016.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=B8F49A21-3249-429F-A96C-D26D5B42C262.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:6EB2
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].CabName=WERInternalMetadata.xml
File[0].Path=WEREE21.tmp.WERInternalMetadata.xml
File[0].Flags=327682
File[0].Type=5
File[0].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE21.tmp.WERInternalMetadata.xml
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=VirtualBox Manager
AppPath=C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=BA86250318F5C32FAFDDB2FFA1A65C77
MetadataHash=-836308217

Attaching: round2_VBox_log.txt

[Fieldy]

Round 2 VBox.log

[SamH]

This is also my experience described here ​https://forums.virtualbox.org/viewtopic.php?f=3&t=100675 and here https://www.alldomusa.eu.org/ticket/20020 .

[fth0]

The VBoxHardening.log file ends with audio related messages, and the round1 VBox.log.1 file and the round2 VBox.log file both contain audio related error messages near their end:

21:16:32.282180 DSound: DirectSound playback initialization failed with ERROR_TOO_MANY_OPEN_FILES 0x88890004
21:16:32.282277 DSound: Error enumeration playback device 'LG HDR WQHD (NVIDIA High Definition Audio)', rc=VERR_GENERAL_FAILURE

For a test, I'd suggest to remove the virtual audio hardware from the VM configuration, and see if the issue persists. If the audio error messages still occur, you could try and change the audio setup of the host.

[SamH]

For me disabling audio in VM settings provided needed stabilization of the machine and now freezing or crashing is no longer happening when screen lock on host happens.

[virtuallyEverywhere]

I am using a Linux OS for the host and also have the Linux guest Full VM Hang. I have no audio related error messages. I never experienced these issues with a Windows guest OS.

But, despite the Full VM Hang when you open up the session information you can clearly see CPU load and RAM usage. The Full VM Hang is still fully not hanging. Additionally, a reboot of the host is not necessary i only need to reset the guest machine. I changed multiple settings and the problem shows up more frequently now.