Re: [fedora-virt] Losing sound in Win XP qemu-kvm guest

[jah]

Thanks for the reply Gilboa.  I had given up on getting a response to my 
email and almost didn't spot it.  It's disappointing that nobody from 
Red Hat feels like it's worth responding to.  The only thing I could 
find in Bugzilla was 520228, a very similar problem with F11 from Aug 
2009.  Though this pertains to my Fedora desktop at home, possibly my 
Red Hat rep at work can find a resource who would share some insight on 
the problem.

Anyway, I switched QEMU_AUDIO_DRV from "alsa" to "pa" and that made
the 
problem worse, sound went out a few minutes after starting the guest.  I 
don't have any experience running KVM under F12 but I am running 
Virtualbox under F12 at work (no hardware virtual extentions) and sound 
works great in my XP guest.  What exactly are the "connection refused" 
messages you're getting from qemu?  The only unusual messages I'm 
getting are occasional bursts of this message:

Jun 11 23:52:51 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
Jun 12 10:10:06 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
Jun 12 11:02:53 host pulseaudio[2651]: ratelimit.c: 685 events suppressed

In Gentoo I only had this problem when I ran KVM as a module, not when 
it was compiled into the kernel.  Unfortunately nowdays compiling a 
custom kernel in Red Hat/Fedora is a little more involved and not really 
worth re-doing every time a new kernel update comes out.

-jah


>  Seeing the same.
>  My script defaults to PA.
>
>  Looking at the console, I see that qemu is getting connection refused.
>  I'd imagine that the problem is that my scripts runs as root (I use only
>  bridged networks), and PA (per-user) is getting rejected.
>
>  What I don't understand is - why it worked just fine under F12, and why
>  it doesn't work now? Though, I have a feeling that this a PA issue - not
>  qemu.
>
>  - Gilboa
>

Losing sound in Win XP qemu-kvm guest

[Justin Forbes]

On Mon, 2010-06-14 at 14:01 -0400, jah wrote:
>  Thanks for the reply Gilboa.  I had given up on getting a response to
> my 
>  email and almost didn't spot it.  It's disappointing that nobody from 
>  Red Hat feels like it's worth responding to.  The only thing I could 
>  find in Bugzilla was 520228, a very similar problem with F11 from Aug 
>  2009.  Though this pertains to my Fedora desktop at home, possibly my 
>  Red Hat rep at work can find a resource who would share some insight on 
>  the problem.
>  
>  Anyway, I switched QEMU_AUDIO_DRV from "alsa" to "pa" and that made
> the 
>  problem worse, sound went out a few minutes after starting the guest.  I 
>  don't have any experience running KVM under F12 but I am running 
>  Virtualbox under F12 at work (no hardware virtual extentions) and sound 
>  works great in my XP guest.  What exactly are the "connection refused" 
>  messages you're getting from qemu?  The only unusual messages I'm 
>  getting are occasional bursts of this message:
>  
>  Jun 11 23:52:51 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
>  Jun 12 10:10:06 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
>  Jun 12 11:02:53 host pulseaudio[2651]: ratelimit.c: 685 events suppressed
>  
>  In Gentoo I only had this problem when I ran KVM as a module, not when 
>  it was compiled into the kernel.  Unfortunately nowdays compiling a 
>  custom kernel in Red Hat/Fedora is a little more involved and not really 
>  worth re-doing every time a new kernel update comes out.
>   
Sorry, I haven't had a chance to reproduce yet, but should get to it in
the next day or two.  Are you running constant audio in the XP guest to
see it, or doing something different?

Justin

Losing sound in Win XP qemu-kvm guest

[jah]

Justin, if I understand you correctly, no I'm not running audio 
continuously in the XP guest (like playing music, etc).  Just normal 
event sounds.  When set to the Sound Blaster, sound will just go away in 
1 - 2 days.  When set to the Intel card, so far, I do not lose sound but 
it doesn't work as well - the sound is choppy.  Thanks for the reply.

-jah


On 06/14/2010 02:59 PM, Justin M. Forbes wrote:
>  Sorry, I haven't had a chance to reproduce yet, but should get to it in
>  the next day or two.  Are you running constant audio in the XP guest to
>  see it, or doing something different?
>
>  Justin
>
>

Losing sound in Win XP qemu-kvm guest

[Dor Laor]

On 06/14/2010 11:03 PM, jah wrote:
>  Justin, if I understand you correctly, no I'm not running audio
>  continuously in the XP guest (like playing music, etc).  Just normal
>  event sounds.  When set to the Sound Blaster, sound will just go away in 
Indeed es1370 emulation is buggy when multiple stream are played - you 
probably lose it when 2 sound events happen in parallel. (I don't know 
more on this issue)

>  1 - 2 days.  When set to the Intel card, so far, I do not lose sound
> but
>  it doesn't work as well - the sound is choppy.  Thanks for the reply. 
AC97 proved to be better in the past, choppiness might be a recent 
regression.

>  -jah
>
>
>  On 06/14/2010 02:59 PM, Justin M. Forbes wrote:
> >
> > Sorry, I haven't had a chance to reproduce yet, but should get to it in
> > the next day or two.  Are you running constant audio in the XP guest to
> > see it, or doing something different?
> >
> > Justin
> >
> >
>
>  _______________________________________________
>  virt mailing list
>  virt(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/virt

Losing sound in Win XP qemu-kvm guest

[jah]

Quoting Dor Laor <dlaor(a)redhat.com&gt;:
>  Indeed es1370 emulation is buggy when multiple stream are played -
> you
>  probably lose it when 2 sound events happen in parallel. (I don't know
>  more on this issue) 
Thanks, that was my observation but it's nice to have confirmation  
from somebody more in the know.

> > 1 - 2 days.  When set to the Intel card, so far, I do not lose
> sound but
> > it doesn't work as well - the sound is choppy.  Thanks for the reply.
>
>  AC97 proved to be better in the past, choppiness might be a recent   
>  regression. 
In Gentoo, AC97 has always worked great, no choppiness.  That's all  
the way up through kernel 2.6.33.  Why would it be different in  
Fedora?  By default Gentoo doesn't use pulse audio.  Could that be the  
difference?  In Fedora, AC97 isn't just choppy, it has a reverb sound.  
  This is with the same XP guest image too.  I'll try to capture a  
sample and post a link.

-jah


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Losing sound in Win XP qemu-kvm guest

[jah]

Quoting Dor Laor <dlaor(a)redhat.com&gt;:
> > Indeed es1370 emulation is buggy when multiple stream are played
> - you
> > probably lose it when 2 sound events happen in parallel. (I don't know
> > more on this issue)
>
>  Thanks, that was my observation but it's nice to have confirmation
>  from somebody more in the know. 
My mistake, it was sb16 that was dropping out for me, not es1370.  But  
similarly, sb16 drops out when there is simultaneous sound from the XP  
guest and Linux.  Playing music in Rhythmbox in Fedora will knock out  
sb16 emulation in the XP guest for example.

ac97 doesn't drop out but is choppy in Fedora.  When booted into  
Gentoo, ac97 sounds great, no choppiness.

Justin, comparing the Fedora qemu.spec file with the Gentoo ebuild and  
compile time options, the only difference related to audio that really  
stands out for me is pulse audio.

Gentoo qemu-kvm-0.12.4 ebuild:

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/qem...

My Gentoo use flags/compile options (indicated by the plus in 1st or  
2nd columns):

# equery u qemu-kvm
[ Searching for packages matching qemu-kvm... ]
[ Colour Code : set unset ]
[ Legend : Left column  (U) - USE flags from make.conf              ]
[        : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for app-emulation/qemu-kvm-0.12.4-r1 ]
  U I
  - + aio                             : Enables support for Linux's Async IO
  + + alsa                            : Adds support for  
media-libs/alsa-lib (Advanced Linux Sound Architecture)
  - - bluetooth                       : Enables Bluetooth Support
  - - curl                            : Adds support for client-side  
URL transfer library
  - - esd                             : Adds support for  
media-sound/esound (Enlightened Sound Daemon)
  - - fdt                             : Enables firmware device tree support
  + + gnutls                          : Adds support for  
net-libs/gnutls (TLS 1.0 and SSL 3.0 support)
  + + hardened                        : activate default security  
enhancements for toolchain (gcc, glibc, binutils)
  - - kvm-trace                       : Allows you to use KVM tracing
  + + ncurses                         : Adds ncurses support (console  
display library)
  - - pulseaudio                      : Adds support for PulseAudio  
sound server
  - - qemu-ifup                       : Provides the qemu-ifup script  
for use with QEMU's built in bridging
  - + qemu_softmmu_targets_arm        : system emulation target
  - + qemu_softmmu_targets_cris       : system emulation target
  - + qemu_softmmu_targets_i386       : system emulation target
  - + qemu_softmmu_targets_m68k       : system emulation target
  - + qemu_softmmu_targets_microblaze : system emulation target
  - + qemu_softmmu_targets_mips       : system emulation target
  - + qemu_softmmu_targets_mips64     : system emulation target
  - + qemu_softmmu_targets_mips64el   : system emulation target
  - + qemu_softmmu_targets_mipsel     : system emulation target
  - + qemu_softmmu_targets_ppc        : system emulation target
  - + qemu_softmmu_targets_ppc64      : system emulation target
  - + qemu_softmmu_targets_ppcemb     : system emulation target
  - + qemu_softmmu_targets_sh4        : system emulation target
  - + qemu_softmmu_targets_sh4eb      : system emulation target
  - + qemu_softmmu_targets_sparc      : system emulation target
  - + qemu_softmmu_targets_sparc64    : system emulation target
  - + qemu_softmmu_targets_x86_64     : system emulation target
  - + qemu_user_targets_alpha         : userspace emulation target
  - + qemu_user_targets_arm           : userspace emulation target
  - + qemu_user_targets_armeb         : userspace emulation target
  - + qemu_user_targets_cris          : userspace emulation target
  - + qemu_user_targets_i386          : userspace emulation target
  - + qemu_user_targets_m68k          : userspace emulation target
  - + qemu_user_targets_microblaze    : userspace emulation target
  - + qemu_user_targets_mips          : userspace emulation target
  - + qemu_user_targets_mipsel        : userspace emulation target
  - + qemu_user_targets_ppc           : userspace emulation target
  - + qemu_user_targets_ppc64         : userspace emulation target
  - + qemu_user_targets_ppc64abi32    : userspace emulation target
  - + qemu_user_targets_sh4           : userspace emulation target
  - + qemu_user_targets_sh4eb         : userspace emulation target
  - + qemu_user_targets_sparc         : userspace emulation target
  - + qemu_user_targets_sparc32plus   : userspace emulation target
  - + qemu_user_targets_sparc64       : userspace emulation target
  - + qemu_user_targets_x86_64        : userspace emulation target
  - - sasl                            : Adds support for the Simple  
Authentication and Security Layer
  + + sdl                             : Adds support for Simple Direct  
Layer (media library)
  - - static                          : !!do not set this during  
bootstrap!! Causes binaries to be statically linked instead of  
dynamically
  - - vde                             : Enable VDE-based networking


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.