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

Re: [Xen-users] PCI Passthrough for Windows error

To: billy lau <billylau1@xxxxxxxxx>
Subject: Re: [Xen-users] PCI Passthrough for Windows error
From: colchaodemola <colchaodemola@xxxxxxxxx>
Date: Sun, 16 Nov 2008 20:13:42 -0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 16 Nov 2008 15:14:59 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=QQoCfZzvVxo6z/4u53rvqS8gGr14RfhJ3e18pwF0N7Y=; b=IXJflR8G6cHEPQaSRh+5JUQcxC+myZaCxXyglnoPcxJPVtHSI7+SEpf00GVTZr/FL+ zdTdPjL+jjCGVWsciVBuIaKBm8Uh381G0ecPPLTTJWysDelO4YbQHawImiK97rQ5o1nK S5eByFh+2FxPG60SgG4iWpygV3DKbA2EgbsXc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=tL9Oz8pyrpVEDjSrhQH+Yj3SkpuL6LbUAftHP7r6TmULof6TowcxT0wKiOwFPYSOhB Fil2TxBkVzhyD3dqTTUpHNvwm8oR1EV/YmSZDRI/uYq59L+M7tzbsyICYoO8gp/hSvw6 T3CpENNLVd1paJXzLLtzsdFdY1Zr6rUbl/Vt4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6b5ba5140811161507qf5bd994h731fd8f79378e653@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: <20487119.post@xxxxxxxxxxxxxxx> <6b5ba5140811161350j3cc4e42ct1e7870e53c34babe@xxxxxxxxxxxxxx> <4920A74C.7070603@xxxxxxxxx> <6b5ba5140811161507qf5bd994h731fd8f79378e653@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20080925)
billy lau wrote:


On Sun, Nov 16, 2008 at 6:05 PM, colchaodemola <colchaodemola@xxxxxxxxx <mailto:colchaodemola@xxxxxxxxx>> wrote:

    billy lau wrote:



        On Sun, Nov 16, 2008 at 4:18 PM, colchaodemola
        <colchaodemola@xxxxxxxxx <mailto:colchaodemola@xxxxxxxxx>
        <mailto:colchaodemola@xxxxxxxxx
        <mailto:colchaodemola@xxxxxxxxx>>> wrote:



           Todd Deshane wrote:
           >
           > On Tue, Nov 11, 2008 at 3:16 PM, billy lau
        <billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>
           <mailto:billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>>> wrote:
           >>
           >>
           >> On Tue, Nov 11, 2008 at 3:13 PM, Todd Deshane
           <deshantm@xxxxxxxxx <mailto:deshantm@xxxxxxxxx>
        <mailto:deshantm@xxxxxxxxx <mailto:deshantm@xxxxxxxxx>>> wrote:
           >>>
           >>> On Tue, Nov 11, 2008 at 3:09 PM, billy lau
        <billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>
           <mailto:billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>>> wrote:
           >>> >
           >>> >
           >>> > On Tue, Nov 11, 2008 at 3:03 PM, Todd Deshane
           <deshantm@xxxxxxxxx <mailto:deshantm@xxxxxxxxx>
        <mailto:deshantm@xxxxxxxxx <mailto:deshantm@xxxxxxxxx>>>

           >>> > wrote:
           >>> >>
           >>> >> On Tue, Nov 11, 2008 at 2:47 PM, billy lau
           <billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>
        <mailto:billylau@xxxxxxxxx <mailto:billylau@xxxxxxxxx>>>

           >>> wrote:
           >>> >> > Hi, sorry, it took me quite a while, because I was
        trying
           other
           >>> ways
           >>> >> > to
           >>> >> > get
           >>> >> > around htis prblem, but it seems like I cannot get
        pass this.
           >>> >> >
           >>> >> > Attached is the output from
           >>> >> > lspci -tv
           >>> >> > lspci -xxx -vvv
           >>> >> > xm pci-list-assignable-devices returns nothing
           >>> >> > ls /sys/bus/pci/drivers/pciback*
           >>> >> > grep hide /boot/grub/menu.lst
           >>> >> >
           >>> >> > The Linux guest taht worked before was PV.
           >>> >> >
           >>> >> > xm dmesg shows
           >>> >> > (XEN) HVM: VMX enabled
           >>> >> > and
           >>> >> > (XEN) I/O virtualisation disabled
           >>> >> > (XEN) Xen trace buffers: disabled
           >>> >> >
           >>> >> > I'm not sure if this means iommu is disabled. If
        it is,
           what should
           >>> I
           >>> >> > do
           >>> >> > to
           >>> >> > enable it? Thanks,
           >>> >> > - billy
           >>> >> >
           >>> >>
           >>> >> There is a separate bios option to enable the IOMMU
        (VT-d) (IO
           >>> >> virtualization support)
           >>> >>
           >>> >> Did you verify that your Chipset support VT-d? That
        is the
           first
           >>> step.
           >>> >
           >>> >
           >>> > Yeah, I made sure that in my bios, under performance,
           virtualization
           >>> is
           >>> > turned on, and also IOMMU is turned on. My chipset is
           Intel(R) Xeon(R)
           >>> > E5430
           >>> > @ 2.66GHz. I googled that up, it supports VT-d. What
        do you
           mean by a
           >>> > _separate_ bios option?
           >>> >
           >>>
           >>> VT (virtualization support) has a bios option, VT-d (IO
           virtualizaiton)
           >>> has
           >>> another.
           >>
           >> I see. Yes, I have confirmed that both options are on in
        the bios.
           >>
           >>>
           >>> Did you turn the computer off (not just restart) after
        setting
           that
           >>> option?
           >>
           >> Yes.
           >>
           >>>
           >>> The xm dmesg should show that I/O virtualization is
        enabled.
           >>
           >> Doing another xm dmesg, it still shows (XEN) I/O
        virtualisation
           disabled.
           >> Any other thoughts on how to turn it on?
           >>
           >
           > What version of Xen?
           >
           > Have you or could you try xen-unstable?
           >
           > Cheers,
           > Todd
           >
           > --
           > Todd Deshane
           > http://todddeshane.net
           > http://runningxen.com
           >
           > _______________________________________________
           > Xen-users mailing list
           > Xen-users@xxxxxxxxxxxxxxxxxxx
        <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
        <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
        <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>>

           > http://lists.xensource.com/xen-users
           >
           >


           I am having the same problem though my architecture is a little
           different.
           I am running red hat 5 ES and compiled xen 3.3 from source ...
           Processor is AMD DUAL OPTERON 2218

           processor       : 0
           vendor_id       : AuthenticAMD
           cpu family      : 15
           model           : 65
           model name      : Dual-Core AMD Opteron(tm) Processor 2218
           SUN ULTRA 40 M2
           I have IOMMU enabled in BIOS, but i always get io
        virtualization
           disabled.
           Am i missing anything ? Does it AMD IOMMU supported ?
           I am gonna try xen unstable and see if it works.


        Did you add the line iommu=1 in the grub's menu on the kernel
        line?
    Yeah. Still can not get it work.


I see. Well, for now, the first thing is to make sure that your machine supports Vt-d. Once you made sure that, then perhaps you could try xen unstable. I too had some problems with Xen 3.3.0 earlier.

- billy
Is VTd available on AMD machines ? I have IOMMU enabled in BIOS , but i dont know it that is the same thing.

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