From: malc <av1474@comtv.ru>
To: Consul <void@aleksoft.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Audio problem
Date: Fri, 15 May 2009 15:34:49 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0905151534290.2190@linmac.oyster.ru> (raw)
In-Reply-To: <guij42$1rs$1@ger.gmane.org>
On Thu, 14 May 2009, Consul wrote:
> Hello,
>
> With the current qemu I experience strange audio problem with some
> configurations
> of Windows XP guests running on Windows XP hosts. When playing anything,
> it sounds rather like a clock ticking than a familiar logon sound.
> Interestingly,
> this happens only if I have enabled a network adapter, no matter if it is
> ne2k_pci
> or rtl8139. The sound hardware doesn't matter either, but if I choose
> net=none,
> the sound magically returns to normal.
>
> Today I actually tried to pinpoint when this problem appeared first, but the
> only thing
> I found is that the last commit which plays the sounds well while the network
> is enabled
> is this one: 023f3329d87a6203d03a0e9ccb948772940da96. It looks like this
> commit has nothing
> to do with audio, but since then I couldn't find any commit that would work.
> There were some commits after that when the sound didn't play at all, but when
> it did,
> the sound was always choppy. I don't think the above mentioned commit caused
> the actual
> problem, but rather exposed another bug which is still there.
qemu$ git cat-file -p 023f3329d87a6203d03a0e9ccb948772940da96
fatal: Not a valid object name 023f3329d87a6203d03a0e9ccb948772940da96
>
> Any hints?
>
> Qemu is compiled with these flags
> ./configure --target-list='i386-softmmu' --static --prefix='/c/qemu-dist'
> --audio-drv-list="dsound"
>
>
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-05-15 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 2:13 [Qemu-devel] Audio problem Consul
2009-05-15 11:34 ` malc [this message]
2009-05-15 16:01 ` [Qemu-devel] " Consul
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=Pine.LNX.4.64.0905151534290.2190@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=qemu-devel@nongnu.org \
--cc=void@aleksoft.net \
/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).