From: Avi Kivity <avi@qumranet.com>
To: David Abrahams <dave@boost-consulting.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] qemu/kvm seems to take ALSA all for itself?
Date: Wed, 23 May 2007 15:28:14 +0300 [thread overview]
Message-ID: <4654335E.7010503@qumranet.com> (raw)
In-Reply-To: <87zm3wcliz.fsf@grogan.peloton>
David Abrahams wrote:
> on Mon May 21 2007, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w-AT-public.gmane.org> wrote:
>
>
>> David Abrahams wrote:
>>
>>> When I have windows XP running under kvm, I get
>>>
>>> dave@grogan:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
>>> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
>>> aplay: main:550: audio open error: Device or resource busy
>>>
>>> As soon as I shut down my VM, though, it works perfectly. Is this
>>> expected behavior?
>>>
>>>
>> I think you have to set up a mixer or something. But I'd rather be deaf
>> than have to wade through all the pseudo-documentation in order to find
>> out how.
>>
>
> Maybe I wasn't sufficiently clear. Sound in the VM works fine; it
> just seems to kill sound in the host... or is the mixer somehow
> supposed to cure that?
>
>
I have a similar problem where running a Java virtual machine kills
sound to other apps. I assume that a mixer will fix this, but have been
unable to get it to work.
Looks like this is a similar problem.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2007-05-23 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 14:29 [Qemu-devel] qemu/kvm seems to take ALSA all for itself? David Abrahams
2007-05-21 14:37 ` [Qemu-devel] Re: [kvm-devel] " Avi Kivity
2007-05-23 2:37 ` [Qemu-devel] " David Abrahams
2007-05-23 12:28 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4654335E.7010503@qumranet.com \
--to=avi@qumranet.com \
--cc=dave@boost-consulting.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).