I would point out that there is a infrastructure in the latest qemu repository to allow a shared memory region between the host and the guest: http://www.linux-kvm.org/wiki/images/e/e8/0.11.Nahanni-CamMacdonell.pdf http://lwn.net/Articles/380869/ On Fri, Sep 24, 2010 at 13:58, Jeremy Nickurak <jeremy at nickurak.ca> wrote: > On Fri, Sep 24, 2010 at 10:19, Tomasz Torcz <tomek at pipebreaker.pl> wrote: > >> Has qemu informed PA about required latency? There's an API for that. >> > > That's a really hard piece of information to provide, in general at the > VM-level, because various applications inside the VM may require different > latency guarantees. > > That said, this makes me wonder if the idea of virtualizing a sound card > isn't the right approach here, and instead, the pulse clients (be they > native or via the alsa pulse plugin) should be contacting a pulseaudio > server on the host? Would it be more feasible to manage latency this way? > > -- > Jeremy Nickurak -= Email/XMPP: -= jeremy at nickurak.ca =- > > -- Jeremy Nickurak -= Email/XMPP: -= jeremy at nickurak.ca =- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20100925/12e24d64/attachment.htm>
