Hi, Is vtd / pci passthru broken in 3.3? On my Supermicro x7dwa-n system I was able to get pci passthru working with 3.2.1, but with 3.3 the xen dmesg states that it is disabled: (XEN) I/O virtualisation disabled I used the same argument to enable vtd as I did with 3.2.1, is this correct: (XEN) Command line: vtd=1 com1=115200,8n1 console=vga,com1 noirqbalance Thanks Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I think iommu=1 is needed to command line. See the folowing howto. http://wiki.xensource.com/xenwiki/VTdHowTo Best Regards, Akio Takebe>Hi, > >Is vtd / pci passthru broken in 3.3? On my Supermicro x7dwa-n system I >was able to get pci passthru working with 3.2.1, but with 3.3 the xen >dmesg states that it is disabled: > >(XEN) I/O virtualisation disabled > >I used the same argument to enable vtd as I did with 3.2.1, is this correct: > >(XEN) Command line: vtd=1 com1=115200,8n1 console=vga,com1 noirqbalance > >Thanks >Andy > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Nov 27, 2008 at 1:40 PM, Akio Takebe <takebe_akio@jp.fujitsu.com> wrote:> Hi, > > I think iommu=1 is needed to command line. > See the folowing howto. > http://wiki.xensource.com/xenwiki/VTdHowTo > > Best Regards, > > Akio TakebeThat is exactly what was wrong, I added iommu=1 and I the xen dmesg now shows "I/O virtualisation enabled" Now I have a different problem, the device I want to pass thru is a 4 port pci usb card, it has 3 functions: 08:03.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 08:03.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 08:03.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) I can pass through 08:03.0 and in my windows hvm some new VIA Rev 5 USB ports are detected and are functional, but they are usb 1.1 not 2.0, if I try to pass through 08:03.1 or 08:03.2 I get a error: ValueError: unsupported format character '':'' (0x3a) at index 6 I applied the fix for this error: http://xenbits.xensource.com/xen-unstable.hg?rev/e2a8e3be7bfa but that just changes the error message to: non-page-aligned MMIO BAR found I am not sure if this error is correct, if 08:03.0 can be passed through successfully shouldn''t the other functions on the same card also be compatible? I tried applying fix_find_parent.patch from http://www.nabble.com/-PATCH--Fix-the-detection-of-the-upmost-bridge-in-the-python-function-find_parent()-td19910861.html in case the parent device was being misidentified but it didnt make any difference. I was reading a thread earlier that seemed to suggest that a patch has been released which enables passthru for non-page-aligned mmio bar devices, unfortunately firefox crashed and now I cannot find the thread again, perhaps already in xen-unstable? Andy http://www.nabble.com/-PATCH--Fix-the-detection-of-the-upmost-bridge-in-the-python-function-find_parent()-td19910861.html _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>>>>>> "andrew.lyon" == Andrew Lyon <andrew.lyon@gmail.com> writes: >> >> andrew.lyon> Hi, >> andrew.lyon> Is vtd / pci passthru broken in 3.3? On my Supermicro >> x7dwa-n system I >> andrew.lyon> was able to get pci passthru working with 3.2.1, but >> with 3.3 the xen >> andrew.lyon> dmesg states that it is disabled: >> >> andrew.lyon> (XEN) I/O virtualisation disabled >> >> andrew.lyon> I used the same argument to enable vtd as I did with >> 3.2.1, is this correct: >> >> andrew.lyon> (XEN) Command line: vtd=1 com1=115200,8n1 >> console=vga,com1 noirqbalance >> >> andrew.lyon> Thanks >> andrew.lyon> Andy >> >> -- >On Tue, Dec 9, 2008 at 11:55 PM, Rui-Tao Dong <rdong@trestlecorp.com> wrote:> > Hi Andrew, > > I have the same exact MB, but couldn''t get it to work with VT-d. What > version of the BIOS did you have on it? > > --I have never updated the BIOS, it came with 1.1b: # dmidecode 2.9 SMBIOS 2.5 present. 57 structures occupying 2109 bytes. Table at 0xBFF66000. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Phoenix Technologies LTD Version: 1.1b Release Date: 08/04/2008 Address: 0xE3740 Runtime Size: 116928 bytes ROM Size: 2048 kB Characteristics: Make sure you have enabled vt-d in the BIOS, if it was disabled you will need to power off the system (shutdown then remove power cord for a few seconds) and then power up for it to be enabled. If you are using Xen 3.3 you need iommu=1, older versions used vtd=1. Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Dec 11, 2008 at 11:59 PM, Rui-Tao Dong <ruitao.dong@gmail.com> wrote:> > Hi Andy, > > Thanks for the reply and sorry about the messed up email address. > > I installed the same version of the BIOS and enabled VT-d & VT and > powered it off for a few minutes. After restarting, I checked to make > sure that VT-d & VT are still enabled. > > I did > > root (hd0,6) > kernel /boot/xen.gz-3.3.0 > module /boot/vmlinuz-2.6.18-92.1.10.el5xen ro vtd=1 iommu=1Thats wrong, you need to pass iommu=1 to xen, not the linux kernel: kernel /boot/xen.gz-3.3.0 vtd=1 iommu=1 Andy> root=LABEL=/CentOS > module /boot/initrd-2.6.18-92.1.10.el5xen.img > > but xm dmesg still tells me > > (XEN) I/O virtualisation disabled. > > -- > Rui-Tao > > > andrew.lyon> I have never updated the BIOS, it came with 1.1b: > > andrew.lyon> # dmidecode 2.9 > > andrew.lyon> SMBIOS 2.5 present. > andrew.lyon> 57 structures occupying 2109 bytes. > andrew.lyon> Table at 0xBFF66000. > > andrew.lyon> Handle 0x0000, DMI type 0, 24 bytes > andrew.lyon> BIOS Information > andrew.lyon> Vendor: Phoenix Technologies LTD > andrew.lyon> Version: 1.1b > andrew.lyon> Release Date: 08/04/2008 > andrew.lyon> Address: 0xE3740 > andrew.lyon> Runtime Size: 116928 bytes > andrew.lyon> ROM Size: 2048 kB > andrew.lyon> Characteristics: > > > andrew.lyon> Make sure you have enabled vt-d in the BIOS, if it was > disabled you > andrew.lyon> will need to power off the system (shutdown then remove > power cord for > andrew.lyon> a few seconds) and then power up for it to be enabled. > > andrew.lyon> If you are using Xen 3.3 you need iommu=1, older > versions used vtd=1. > > andrew.lyon> Andy >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users