From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tom Rotenberg <tom.rotenberg@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problems with audio device pass-through with the latest xen-unstable
Date: Mon, 14 Dec 2009 10:28:54 -0500 [thread overview]
Message-ID: <20091214152854.GE28440@phenom.dumpdata.com> (raw)
In-Reply-To: <8686c3cd0912140730m749cd2f0uc95fc2ce7235bdcd@mail.gmail.com>
On Mon, Dec 14, 2009 at 05:30:16PM +0200, Tom Rotenberg wrote:
> Hi,
>
> I'm using the latest xen-unstable (changeset:20605:8f304c003af4), and
> i found out, that for some reason, there is a problem with audio
> pass-through on my Lenovo machines (i have tested it on both Lenovo
> X200 & Lenovo T400/T500). The problem is, that fater i pass-through
> the audio device (00:1b.0 Audio device: Intel Corporation 82801I (ICH9
> Family) HD Audio Controller (rev 03)), to the domU Windows XP, it
> doesn't identify any audio/media device. i have made sure, i have the
> Microsft UAA high-definition audio bus driver, and i still don't see
> any audio device.
>
> It looks like a specific problem, because on a Dell e6400 machine the
> audio pass-through works fine.
>
> Does anyone knows about such issue? or can guide me to where the
> problem might be?
Could you send me the lspci -vvv output of both devices? That is the one
working and non-working.
Also is there anything in the QEMU log?
One of the items that has not yet been back-ported from 2.6.18 is
making the BARs page-aligned... and I wonder if that is what you
are hitting (thought the more I think about it the less I think it is that
- the xm code will give you a fat warning about this).
next prev parent reply other threads:[~2009-12-14 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 15:30 Problems with audio device pass-through with the latest xen-unstable Tom Rotenberg
2009-12-14 15:28 ` Konrad Rzeszutek Wilk [this message]
2009-12-14 15:52 ` Tom Rotenberg
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=20091214152854.GE28440@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=tom.rotenberg@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.