Ticket #19158 (new defect)

Opened 3 years ago

Last modified 2 years ago

VirtualBox and bluetooth earbuds

Reported by: superme Owned by:
Component: audio Version: VirtualBox 6.1.0
Keywords: Cc:
Guest type: Windows Host type: Windows


Host: Windows 10 (all updates) Guest: Windows 10 (all updates) Earbuds: Bluetooth Sony wf-1000xm3 (firmware 2.03)

Connected earbuds to host, guests detect and no issues. Once earbuds disconnected from host and connected again, guest can not detect the audio coming from host via earbuds (sound via speakers and wired earnphones works well)

Change History

comment:1 Changed 3 years ago by socratis

  1. It's usually better and faster, if issues get first addressed in the  VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, is going to help you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

  1. 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.

So, please open a new thread in the  VirtualBox on Windows Hosts section of the forums.

comment:2 Changed 3 years ago by boxer01

Please take a look at  this discussion in the forum. It looks like you have a similar problem. Then you probably would like to have a look on the connected tickets like #18695, #18404, #17225#comment:55.

comment:3 Changed 2 years ago by boxer01

Take a look at the #18594 and the version 6.1.17 build 141128. This one looks like to be solved.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use