qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	kvm@vger.kernel.org, Stefan Pietsch <stefan.pietsch@lsexperts.de>
Subject: [Qemu-devel] Re: KVM: High CPU load with audio enabled
Date: Tue, 09 Nov 2010 09:27:42 +0100	[thread overview]
Message-ID: <4CD905FE.20204@web.de> (raw)
In-Reply-To: <4CD88C58.9030501@msgid.tls.msk.ru>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Am 09.11.2010 00:48, Michael Tokarev wrote:
> 08.11.2010 15:40, Stefan Pietsch wrote:
>> Hi,
>>
>> I'm running a Windows XP guest in KVM. After enabling the audio support
>> (-soundhw es1370) the CPU load of the KVM process in the host system
>> goes up to 100%.
>>
>> Tested with: qemu-kvm-0.13.0 Debian 0.13.0+dfsg-1
>>
>> KVM start command: kvm -m 512 -hda xp.img -soundhw es1370
>>
>> Did you experience similar problems?
> 
> Yes, sound in 0.13 appears to be broken.  It is looping in
> select/read loop forever, read returns EAGAIN and select
> says the filedescriptor is ready.

Try to set QEMU_AUDIO_DAC_TRY_POLL=0 for the environment of the qemu
process. That's long required to get sound out of the Musicpal emulation
as well (malc, you may recall this). It even got worse with current
qemu.git: previously, the sounds was just quirky. Now the system is
booting way slower in polling mode and is partially not reactive anymore.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

       reply	other threads:[~2010-11-09  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101108133310.NDW2tl7gaq4uLMdHXOT0UP@consulting.lsexperts.de>
     [not found] ` <4CD88C58.9030501@msgid.tls.msk.ru>
2010-11-09  8:27   ` Jan Kiszka [this message]
2010-11-09 13:48     ` [Qemu-devel] Re: KVM: High CPU load with audio enabled malc
2010-11-09 14:33       ` Michael Tokarev
2010-11-09 14:41         ` Michael Tokarev
2010-11-10  9:39           ` Stefan Pietsch
2010-11-10 10:18             ` Michael Tokarev

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=4CD905FE.20204@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefan.pietsch@lsexperts.de \
    /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).