On Thursday 29 March 2007, Frank Mehnert wrote:
> On Thursday 29 March 2007, Frank Mehnert wrote:
> > On Wednesday 28 March 2007, Jim Popovitch wrote:
> > > On Wed, 2007-03-28 at 21:50 +0200, Frank Mehnert wrote:
> > > > No idea so far how to solve Jim's problem ...
> > >
> > > Question:  Who cares about Jim's problem? ^W^W^W^W^W^W^  Opps! ;-) 
> > > What I meant to say is: do you know if VBox tries to gain an exclusive
> > > lock on /dev/dsp (or whatever), and if it doesn't get exclusivity does
> > > it do something different and continue.  As I mentioned before, if
> > > /dev/dsp is in use (i.e. mplayer is running) when VBox starts, then
> > > VBox continues to work as expected.  However if VBox is started first,
> > > no other application can play sound until the VBox guest is
> > > stopped/suspended.
> >
> > Vladimir already wrote that ALSA does not open /dev/dsp (it uses
> > /dev/snd/* instead) You can verfiy that with
> >
> >   strace -f -s1024 -o ~/VBoxSDL.log /usr/bin/VBoxSDL -vm <VM name>
>
> Hmm, just did some investigation and saw that I have the same problem when
> running a Linux 2.6.17 kernel or older. In that case, libasound2 starts a
> dmix server which appearently doesn't work right. 2.6.18+ does not need
> such a server and therefore work fine.

We fixed a problem which prevented the ALSA sound server (which is started
by libasound on kernels <= 2.6.17) from starting. The fix will be included
in the next release.

Kind regards,

Frank
-- 
## InnoTek Systemberatung GmbH, http://www.innotek.de ##

Attachment: pgptlBc7eQTLy.pgp
Description: PGP signature

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to