I''m trying to find a way to get around hvm domains completely taking over your sound system. Has anyone successfully setup pulseaudio, or any other sound server, for this purpose? and would be willing to share the steps you followed? In particular, I would like to know what modules you loaded in dom0 (my sound server) and domu, & how you setup network discovery of the sound server. Also, what is the syntax for the variable PULSE_SERVER? I''ve tried the hostname, localhost, and the corresponding ips. The pulseaudio wiki is very skimpy, _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi> I''m trying to find a way to get around hvm domains completely taking over your > sound system. Has anyone successfully setup pulseaudio, or any other sound > server, for this purpose? and would be willing to share the steps you > followed?1 - make sure sound works on dom0 2 - install pulse audio 3 - make pulseaudio accept network connections: load-module module-esound-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 4 - install winesd on hvm windows (just follow the instructions on the page): http://www.clingman.org/winesd/ wfm -- Christian Lyra PoP-PR/RNP _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday April 21 2008 10:42:21 pm Christian Lyra wrote:> load-module module-esound-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 > load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16Thanx for the tip. Unfortunately, I''m getting this in syslog: Apr 22 20:25:59 Insp6400 pulseaudio[8798]: socket-server.c: bind(): Address already in use Apr 22 20:25:59 Insp6400 pulseaudio[8798]: socket-server.c: bind(): Address already in use Apr 22 20:25:59 Insp6400 pulseaudio[8798]: module.c: Failed to load module "module-native-protocol-tcp" (argument: "auth-anonymous=1"): initialization failed. Apr 22 20:25:59 Insp6400 pulseaudio[8798]: module-gconf.c: pa_module_load() failed Apr 22 20:25:59 Insp6400 pulseaudio[8798]: socket-server.c: bind(): Address already in use Apr 22 20:25:59 Insp6400 pulseaudio[8798]: socket-server.c: bind(): Address already in use Apr 22 20:25:59 Insp6400 pulseaudio[8798]: module.c: Failed to load module "module-esound-protocol-tcp" (argument: "auth-anonymous=1"): initialization failed. Apr 22 20:25:59 Insp6400 pulseaudio[8798]: module-gconf.c: pa_module_load() failed and pabrowse still doesn''t work from another machine on my net - 192.168.1.0/24 (which I plugged into your load-modules above). I''ll check out your winesd link later. Thanx. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday April 21 2008 10:42:21 pm Christian Lyra wrote:> oad-module module-esound-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 > load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 > > 4 - install winesd on hvm windows (just follow the instructions on the > page): > > http://www.clingman.org/winesd/Ok - I take it back. Despite the syslog errors, I''m able to make a connection to my dom0 sound server from my fedora rawhide pv domu. Then I tried winesd. Too bad it doesn''t seem there has been any development since 2000. It works, but with a lot of skips and repeats in my winxp hvm. Plus it seems like pulseaudio gets overwhelmed very easily, and exits. I''ll try experimenting with realtime or nice-ing. To answer my previous question about the format of the PULSE_SERVER variable, it''s just like the format of the registry key the winesd page has you setup - ''hostname:port#''. Port# is 16001 for winesd. On linux, 4713 worked for me. I would imagine 16001 would work also (for esd). Thanx. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
jim burns wrote:> > On Monday April 21 2008 10:42:21 pm Christian Lyra wrote: > > oad-module module-esound-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 > > load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/16 > > > > 4 - install winesd on hvm windows (just follow the instructions on the > > page): > > > > http://www.clingman.org/winesd/ > > Ok - I take it back. Despite the syslog errors, I''m able to make a connection > to my dom0 sound server from my fedora rawhide pv domu. > > Then I tried winesd. Too bad it doesn''t seem there has been any development > since 2000. It works, but with a lot of skips and repeats in my winxp hvm. > Plus it seems like pulseaudio gets overwhelmed very easily, and exits. I''ll > try experimenting with realtime or nice-ing. > > To answer my previous question about the format of the PULSE_SERVER variable, > it''s just like the format of the registry key the winesd page has you > setup - ''hostname:port#''. Port# is 16001 for winesd. On linux, 4713 worked > for me. I would imagine 16001 would work also (for esd).Forget winesd, on the Xen PV have snd-dummy loaded. If you are using X-Windows and XDMCP to connect to your remove hosts you can have them set the PULSESERVER on login by querying out the hostname on the $DISPLAY string and setting a global environment variable. I use KDE and kdm which has a /etc/kde/env directory where it whatever script you have there on login to set global environment variables. In this directory I have: /etc/kde/env/pulse.sh: PULSE_SERVER="${DISPLAY%%:*}" if [ -n "${PULSE_SERVER}" ]; then export PULSE_SERVER fi /etc/kde/env/esd.sh ESPEAKER="${DISPLAY%%:*}" if [ -n "${ESPEAKER}" ]; then export ESPEAKER export ESDDSP_MIXER=1 fi Maybe gdm has similar environment setup? Oh, if you are using a distro where alsa isn''t auto redirected to pulse you will need the pulse-libs, alsa-pulse plugin and an asound.conf like: /etc/asound.conf: pcm.pulse { type pulse } ctl.pulse { type pulse } pcm.!default { type pulse } ctl.!default { type pulse } -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday April 23 2008 11:38:16 am Ross S. W. Walker wrote:> Forget winesd, on the Xen PV have snd-dummy loaded. If you are using > X-Windows and XDMCP to connect to your remove hosts you can have them set > the PULSESERVER on login by querying out the hostname on the $DISPLAY > string and setting a global environment variable.Thanx for the detailed configs, but I''m not having any problem with my PV domain. I just set my PULSE_SERVER, and it works w/o any further fuss, or latency problems. It''s my Windows XP hvm I''m having trouble with, which is using winesd. I''ve just finished experimenting with realtime scheduling for the pulseaudio server, and it didn''t help - the sound still skips/repeats. This leads me to believe it is not the server that''s not fast enough, but the hvm that isn''t supplying sound packets fast enough. Probably this is from either the overhead of an hvm domain, or winesd is a really sucky driver. Nothing in Device Manager for the Enlightenment Driver seems to be configurable. If I find anything that helps, I''ll report back. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > It''s my Windows XP hvm I''m having trouble with, which is using winesd. I''ve > just finished experimenting with realtime scheduling for the pulseaudio > server, and it didn''t help - the sound still skips/repeats. This leads me to > believe it is not the server that''s not fast enough, but the hvm that isn''t > supplying sound packets fast enough. Probably this is from either the > overhead of an hvm domain, or winesd is a really sucky driver. Nothing in > Device Manager for the Enlightenment Driver seems to be configurable. >Mine used to work ok... didnt tried with lots of windows hvms running and sending sound at the same time. But my guess is that the skips has to do with windows/xen network not [win]esd. -- Christian Lyra PoP-PR/RNP _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday April 21 2008 10:42:21 pm Christian Lyra wrote:> http://www.clingman.org/winesd/Little bit of an update. My initial impressions were based on AOL Radio performance. Turns out that LaunchRadio (Yahoo!) and Rhapsody play just fine, with minor pauses. I would imagine that this has to do with (the old) Aol Radio''s use of AOlMediaPlaybackControl.exe in a parent child pair of procs. I assume one is doing net io, and the other is doing sound with buffers passed by the net io process. I would imagine a non pv approach to this inter-process communication would be very expensive in an hvm environment. (As far as the new Aol Radio goes, what ever JavaScript it''s using makes it too slow for hvm. It keeps on buffering, with brief bursts of sound, then gives up. Wine has the same problem.) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users