-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virtio-sound #929
Comments
Hi @Mingwang-Li , I would separate two topics:
|
@YanVugenfirer hello! FYI I am in the process of merging a virtio-snd device in upstream QEMU: https://lore.kernel.org/qemu-devel/[email protected]/ PS: To make an uneducated guess: According to this documentation page, the port-miniport driver model corresponds to ALSA's design, so perhaps a new device driver can take advantage of that and have little glue code. |
@epilys nice to meet you! yes, the moment we will start the work supporting virtio-sound on Windows, miniport driver will be needed. How are the upstream reviews going? |
Progressing steadily, as always there's lots of important work the list and objectively virtio-sound is a low priority :) |
@YanVugenfirer nice to meet you! I am glad to hear that you are working on the Windows driver for virito-snd. |
@YanVugenfirer Isn't the virtio-snd specification based, at least in part, on the Intel High Definition Audio specification, which in turn is part of Microsoft's Universal Audio Architecture? As I understand from this documentation, that was done deliberately, to make it possible to add support for virtio-snd to a unified HDA driver. Nice to see support for I'm curious about the possible improvements in terms of CPU utilization and latency that a paravirtualized sound driver could offer over an emulated HDA device, or an emulated USB audio device for that matter. Thanks for your efforts, everyone. |
@volkertb |
Relevant news: QEMU 8.2 was recently released, which finally supports Of course, it would still be great if mvisor and other hypervisors would also gain support for it. Increased adoption, choice and competition is always good. 🙂 |
I also just submitted a Feature Request to the Cloud Hypervisor project. I hope they will take it into consideration. 🤞 |
Hey, this is interesting! Judging from these commits, it would appear that the VirtualBox developers are currently working on virtio-sound as well, apparently because they are adding support for ARM VMs. 🙂
|
In response to my feature request for virtio-snd support, one of the Cloud Hypervisor developers asked the following question:
I mentioned a few I could think of (notably cloud gaming), but perhaps others here have other good examples, which could help convince them to add support for virtio-snd? If so, please share them in the issue thread. Thanks! 🙂 |
hi, i'm just a enduser no programmer. |
Hi all, |
@ybendito But since the virtio-snd device is designed from the ground up to be paravirtualized, wouldn't it at the very least reduce emulation overhead? Preventing the need for port-trapping, unnecessary VMExits, the complexity of having to emulate specific hardware devices, etc? And honestly, I wouldn't consider VirtIO a "proprietary" bus. It's the industry standard for paravirtualized device drivers, blessed by OASIS. |
Hello @YanVugenfirer ,may I ask if it's related to the feature about the work supporting virtio-sound on Windows, |
Hi @anyboo, yes this is am issue about virtio-sound support |
@YanVugenfirer nice to meet you! |
@anyboo, unfortunately, we don't have current plans to start working on virtio-snd. However, having interest from the community might change the plans in the future. I am also OK with supporting someone who want to take on himself the development. |
The VIRTIO specification defines a sound device, do you have any plans to develop this driver and simulate this device on QEMU?
The text was updated successfully, but these errors were encountered: