VirtualBox

Opened 4 weeks ago

Last modified 10 days ago

#22267 new defect

Sound stops working after "switch user" screen if Hyper-V is enabled

Reported by: Mikhail Kovalev Owned by:
Component: other Version: VirtualBox-7.1.4
Keywords: Cc:
Guest type: all Host type: Windows

Description

If I leave a VM running, go to "switch user" screen and then login back to Windows, the sound in the VM is not working until the VM is restarted. This happens only if Hyper-V is enabled in Windows.

In the log I can see errors:

00:26:14.215437 WasAPI: GetCurrentPadding([WasAPI] Front:0) failed during playback: AUDCLNT_E_DEVICE_INVALIDATED (@0x0)
00:26:14.229000 WasAPI: GetCurrentPadding failed on '[WasAPI] Front:0': AUDCLNT_E_DEVICE_INVALIDATED

Attachments (2)

VBox.log.zip (39.5 KB ) - added by Mikhail Kovalev 4 weeks ago.
VBox-2025-01-02-12-56-52.zip (191.4 KB ) - added by Mikhail Kovalev 2 weeks ago.
Audio debug log

Download all attachments as: .zip

Change History (6)

by Mikhail Kovalev, 4 weeks ago

Attachment: VBox.log.zip added

comment:1 by boxer01, 4 weeks ago

I had a similar ticket with invalid device because of the hardware output device switch on the host. But this was fixed a year ago. Strange that this still happens in your other scenario. Hopefully it would be fixed too. BTW, you should update your guest additions.

comment:2 by pentagonik, 4 weeks ago

Please create a verbose audio log, try reproducing the issue and attach it to this defect.

The following Wiki article explains how to achieve this: https://www.virtualbox.org/wiki/AudioDebug

Thanks!

by Mikhail Kovalev, 2 weeks ago

Audio debug log

comment:3 by Mikhail Kovalev, 2 weeks ago

I've uploaded a verbose audio log. While doing the tests today I noticed that the problem does not happen on every try. To reproduce it reliably I need to detach power cord from the laptop (which results in lower CPU frequency).

comment:4 by bird, 10 days ago

Thanks for the logs.

It is probably a variation of the issue mentioned by boxer01 in comment 1 where we keep using a stale device config cache entry.

My guess would be that we're getting some OnDeviceStateChanged notification calls and we're just not responding correctly to these. There is a big @todo in DrvHostAudioWasMmNotifyClient::OnDeviceStateChanged.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette