From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Erik Lotspeich <erik@lotspeich.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux KVM, Windows 7 guest choppy sound
Date: Sun, 09 Sep 2012 17:50:10 +0300 [thread overview]
Message-ID: <504CACA2.7050203@redhat.com> (raw)
In-Reply-To: <504B23BB.2080407@web.de>
On 09/08/2012 01:53 PM, Jan Kiszka wrote:
> On 2012-09-07 18:09, Erik Lotspeich wrote:
>> Hi,
>>
>> I apologize if this isn't the right venue for this message, but this
>> mailing list seems a bit more active than qemu-discuss.
>>
>> Background:
>> I am running OpenSUSE 12.1. I fixed audio issues in VM guests by setting
>> the following in qemu.conf:
>>
>> vnc_allow_host_audio = 1
>>
>> I also set user= and group= to allow qemu-kvm to run as the same user as
>> I am logged in as. This allowed qemu-kvm to send audio to pulseaudio.
>>
>> My issue:
>> I am using the ICH6 virtual audio driver in my VMs. In my Linux VMs, the
>> sound works perfectly without any issues. In my Windows 7 VM, the sound
>> works with the exception of static and choppiness in the audio. Has
>> anyone else seen this or have any ideas for a fix?
>
> Known issue, likely unfixable in QEMU due to hard-coded constraints of
> the driver Windows uses (too small playback buffers).
Would using real-time priority for the guest improve things?
Of course that can be dangerous if the guest decides to spin and has as
many vcpus as you have cores.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-09 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 16:09 [Qemu-devel] Linux KVM, Windows 7 guest choppy sound Erik Lotspeich
2012-09-08 10:53 ` Jan Kiszka
2012-09-09 14:50 ` Avi Kivity [this message]
2012-09-10 9:06 ` Jan Kiszka
2012-09-10 9:12 ` Avi Kivity
[not found] ` <504F4948.3020809@lotspeich.org>
2012-09-11 14:34 ` Jan Kiszka
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=504CACA2.7050203@redhat.com \
--to=avi@redhat.com \
--cc=erik@lotspeich.org \
--cc=jan.kiszka@web.de \
--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).