In the VM configuration, Audio Input seems to be disabled. While the VM is running, there are a lot of events enabling/disabling audio input. When the VM is suspended and resumed for the last time, there are two error messages.
WXP_S4-2020-01-24-13-29-39.log wrote: 18:34:20.151649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002e00!!! 18:34:20.151663 18:34:20.151664 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ff9a82d8201 18:34:20.151672 ExceptionInformation[0]=0000000000000001 18:34:20.151678 ExceptionInformation[1]=0000000000000021 [...] 18:34:20.153376 Thread ID: 0000000000002e00 18:34:20.153387 Thread name: EMT [...] 18:34:20.154315 Xcpt PC : 00007ff9a82d8201 - 0x00028201 bytes into C:\Windows\System32\dsound.dll
The VirtualBox Execution Manager Thread [EMT] executes code in C:\Windows\System32\dsound.dll that tries to write [0x0000000000000001] to a small memory address [0x0000000000000021], triggering an ACCESS_VIOLATION [0xc0000005] exception.
Regarding the different suspend/resume behavior:
WXP_S4-2020-01-24-13-29-39.log wrote: 00:12:47.576074 Pausing VM execution, reason 'host suspend' [...] 01:37:15.246488 Resuming VM execution, reason 'host resume' [...] 18:34:20.127365 Pausing VM execution, reason 'host suspend'
The Windows XP guest is running when the host is manually suspended, so it is automatically suspended by VirtualBox. Afterwards, the host is automatically resumed and suspended several times, and VirtualBox also resumes and suspends the Windows XP guest. During one of the automatic suspensions, the Windows XP guest crashes [around 18 hours and 34 minutes].
ubu3-2020-01-24-15-51-34.log wrote: 00:00:50.522195 Console: Machine state changed to 'Paused' [...] 01:39:02.138443 Resuming VM execution, reason 'host resume' 01:39:02.138477 Ignoring VM resume request, VM was not suspended due to host-suspend [...] 20:57:28.873761 Resuming VM execution, reason 'host resume' 20:57:28.873778 Ignoring VM resume request, VM was not suspended due to host-suspend [...] 20:57:50.675367 DSound: Starting to capture failed with ERROR_CALL_NOT_IMPLEMENTED 0x88780078 [...] 20:57:50.753947 Console: Machine state changed to 'Running'
The Ubuntu guest is manually suspended before the host is manually suspended. Afterwards, the host is automatically resumed and suspended several times, and VirtualBox keeps the Ubuntu guest in the suspended state. When the Ubuntu guest is manually resumed [around 20 hours and 57 minutes], it exhibits the same crash as the Windows XP VM.
Since the crashes are audio related, I suggest to try and fiddle with the audio setup. If you enable audio input in the VM configurations, do the error messages and the crashes persist?
Edit: The 3rd log file also fits the bill.
Additionally, I noticed that audio input was enabled in the Ubuntu guest and disabled in the Windows XP guest. This combination may very well be the key to reproduce the crashes ...
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Virtual machines enter the paused state due to low disk free space
- Article
- 02/23/2023
In this article
This article provides a resolution for the issue that Virtual machines enter the paused state due to low disk free space.
Applies to: Windows Server 2012 R2 Original KB number: 2486243
Symptoms
Consider the following scenario:
- You install the Hyper-V role on a computer that is running Windows Server 2008 or Windows Server 2008 R2.
- You create some virtual machines and store their VHD files into a local hard drive.
- You attempt to start these virtual machines.
In this scenario, you are unable to start these virtual machines. Their states are changed to "Critical - Paused". You receive the error message "Unable to connect to the Virtual machine Manager Server vmm. The attempt to connect timed out" when you attempt to connect these virtual machines by using System Center Virtual Machine Manager admin console.
In addition, the event below is added into the Microsoft-Windows-Hyper-V-VMMS-Admin log:
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: Event ID: 16060 Task Category: None Level: Error Keywords: User: SYSTEM Computer: Description: has been paused because it has run out of disk space on ''
Cause
The hard drives that store these VHD files or snapshots of these virtual machines are out of disk free space.
Resolution
To fix the issue, free disk space on these hard drives or move these VHD files to a new location.
More information
In a particular scenario where you have Virtual Machines configured in Cluster Shared Volume [CSV], and if the CSV disk runs out of free space, the VMs enter into paused state. However, the Virtual Machines on the other nodes of the cluster that do not own the CSV are not affected.
Following event is added into the Microsoft-Windows-Hyper-V-VMMS-Admin log:
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: Event ID: 16050 Task Category: None Level: Warning User: SYSTEM Computer: Description: is about to run out of disk space on ''
The node that owns the Cluster Shared Volume keeps checking the disk space and warns. When the warning is received, the Virtual machine's go into the paused critical state. The Node that doesn't own the CSV, will not have any ways to determine if it is running out of space on CSV volume and hence will allow the virtual machines to run the cluster nodes that don't own the CSV.