WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: Xen domu state in blocking for vt-d hardware access

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: Xen domu state in blocking for vt-d hardware access
From: cocoa <cocoa117@xxxxxxxxx>
Date: Fri, 7 Oct 2011 13:34:51 +0100
Delivery-date: Fri, 07 Oct 2011 05:35:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=dhYC04VxVdbgkjibOMVyiWzP49MFhJ5chGq2LyvfAXI=; b=s7x4TN7EXXBnuupk5dqKz1wcPr76qPybEzMCh2GZvEegvk4BqMoriYG689/Hgwvqn8 7is1Afaco/wuKeWSBUfaogjYs5W3atEo4TSIwZLcGJMmAqejj40jrnWrm70SYsQJ6lSn n/AZaPhp2QPdz1z9lW4ssUc99CmSLc+G5TNoU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAB8A4weXxuzASnxoaO6rCHJ06Vr55Zd7b7NaUN9ZeKjxwOnbXA@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <CAB8A4weXxuzASnxoaO6rCHJ06Vr55Zd7b7NaUN9ZeKjxwOnbXA@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I just found following error message in my PV-domU kernel message. It
seems the sound driver hda-intel is not happy with something.

debian kernel: [    1.846964] HDA Intel 0000:00:00.0: enabling device
(0000 -> 0002)
debian kernel: [    1.847249] HDA Intel 0000:00:00.0: Xen PCI enabling IRQ: 22
debian kernel: [    1.928045] hda_codec: ALC268: BIOS auto-probing.
debian kernel: [    1.928661] input: HDA Digital PCBeep as
/devices/pci-0/pci0000:00/0000:00:00.0/input/input2
debian kernel: [    2.204074] Adding 1048568k swap on /dev/xvda1.
Priority:-1 extents:1 across:1048568k SS
debian kernel: [   16.211113] EXT3 FS on xvda2, internal journal
debian kernel: [  120.439953] hda-intel: Invalid position buffer,
using LPIB read method instead.
debian kernel: [  120.439985] hda-intel: IRQ timing workaround is
activated for card #0. Suggest a bigger bdl_pos_adj.

Cheers

On 7 October 2011 12:58, cocoa <cocoa117@xxxxxxxxx> wrote:
> Hi,
>
> I am running Xen 4.0.1 with Debian Squeeze dom0. I have VT-D enabled
> motherboard, and has confirmed working for vt-d PCI passthrough. When
> I am trying to passthrough on-board sound card
> "00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
> Controller (rev 02)"
> I found both PV-domU and HVM domU does NOT function well with this
> sound card at all. There are always huge noise from speaker. So I
> tested the sound card and speaker, which both functioning fine under
> dom0. I then found the sound card does produce same quality sound as
> long as the domU guest running stats is in r (running), if it stay in
> b (blocking) then there is either no sound at all or just noise.
>
> I get the domU running stats from
> sudo xm list
>
> Name                                        ID   Mem VCPUs      State   
> Time(s)
> Domain-0                                     0   508     1     r-----   2011.5
> ares                                        15  2048     1     r-----   7778.3
> palace                                      14   512     1     -b----   2885.3
> palace-test                                 16   512     1     -b----     63.8
>
> Just to be clear the domU guest I have tested with vt-d PCI
> passthrough is HVM win7 32 bit, and PV-domU debian Squeeze.
>
> I tried to solve the "issue" by doing following, and none of them worked.
>
> 1. pin the dom0 to specific CPU core, e.g. 0, and assign domU to
> different core e.g. 1-3.
> 2. change xm sched-credit -d <domain> -w 65595 or other higher then default 
> 256.
>
> So my question is how to allow domU guest to stay in runing, so it can
> have access to the sound card all the time. At the moment, it seems
> something keep making it changing to blocking status, which clearly
> make impossible to play music. Or this is a bug.
>
> Regards
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>