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-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1

To: chris <tknchris@xxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 29 Nov 2010 22:28:16 +0200
Cc: Xen-Devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 29 Nov 2010 12:29:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTik2MQAc-0E=EAZsA0xY=YrtFSrt9ZGhZRe20-uL@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTika_RqMaPcZUVoiRN_p1dMza7+rf8=wZMXVSOE4@xxxxxxxxxxxxxx> <20101129184240.GY2754@xxxxxxxxxxx> <AANLkTik2MQAc-0E=EAZsA0xY=YrtFSrt9ZGhZRe20-uL@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Nov 29, 2010 at 02:48:08PM -0500, chris wrote:
> ok here is the logs with 2.6.32.26 using pasi's config for 2.6.32.25
> and iommu=verbose at boot. unfortunately this board doesnt have serial
> and i dont have a spare serial card handy, so hopefully this will help
> us figure it out :)
> 

Yep, this is the needed info.


> On Mon, Nov 29, 2010 at 1:42 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > On Mon, Nov 29, 2010 at 11:13:18AM -0500, chris wrote:
> >> Hello,
> >>
> >> I'm having problems with VTD on this board. The board/cpu/bios all
> >> support vt-d and I think maybe I'm just missing something?
> >> Any feedback would be much appreciated :)
> >>
> >> Output below:
> >>
> >
> > Please add "iommu=verbose" option for xen.gz in grub.cfg,
> > then reboot and then paste full Xen hypervisor "xm dmesg" output.
> >
> > -- Pasi
> >
> >> root@vm:~# xm create /etc/xen/vm-nine.cfg
> >> Using config file "/etc/xen/vm-nine.cfg".
> >> Error: Failed to assign device to IOMMU
> >> (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
> >>
> >> pci=['05:00.0','05:00.1','05:00.2']
> >>
> >> root@vm:~# dmesg | grep seiz
> >> [    1.880424] pciback 0000:05:00.0: seizing device
> >> [    1.880482] pciback 0000:05:00.1: seizing device
> >> [    1.880539] pciback 0000:05:00.2: seizing device
> >>
> >> root@vm:~# cat /boot/grub/grub.cfg  | grep pciback
> >>         module  /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> >> root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro
> >> pci=resource_alignment=05:00.0 xen-pciback.permissive
> >> xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2)
> >>

> (XEN) Xen version 4.0.1 (Debian 4.0.1-1) (waldi@xxxxxxxxxx) (gcc version 
> 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) ) Fri Sep  3 15:38:12 UTC 2010
> (XEN) Bootloader: GRUB 1.98+20100804-8
> (XEN) Command line: placeholder iommu=verbose

..

> (XEN) [VT-D]dmar.c:687: Host address width 39
> (XEN) [VT-D]dmar.c:702: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fe711000
> (XEN) [VT-D]iommu.c:1081: drhd->address = fe711000 iommu->reg = 
> ffff82c3fff57000
> (XEN) [VT-D]iommu.c:1083: cap = c9008010e60262 ecap = f0207a
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1b.0
> (XEN) [VT-D]dmar.c:702: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fe710000
> (XEN) [VT-D]iommu.c:1081: drhd->address = fe710000 iommu->reg = 
> ffff82c3fff56000
> (XEN) [VT-D]iommu.c:1083: cap = c90780106f0462 ecap = f020fa
> (XEN) [VT-D]dmar.c:341:   IOAPIC: f0:1f.7
> (XEN) [VT-D]dmar.c:412:   flags: INCLUDE_ALL
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e9000 end_address e9fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr ea000 end_address eafff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr eb000 end_address ebfff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e6000 end_address e6fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e7000 end_address e7fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1a.2
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr e8000 end_address e8fff
> (XEN) [VT-D]dmar.c:707: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:335:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:579:   RMRR region: base_addr ec000 end_address eefff
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 3066.868 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) EPT supports 2MB super page.
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) Intel VT-d Snoop Control not supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping supported.
> (XEN) I/O virtualisation enabled
> (XEN)  - Dom0 mode: Relaxed

..

> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:10.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:10.1
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.0
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.1
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:14.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:14.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:19.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1a.7
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 0:1b.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1d.7
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 0:1f.3
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 3:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 5:0.2
> (XEN) [VT-D]iommu.c:1332: d0:PCIe: map bdf = 7:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:2.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:2.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.4
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.5
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.6
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 8:3.7
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:0.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:0.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:2.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:2.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:3.4
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:4.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:5.3
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.0
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.1
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.2
> (XEN) [VT-D]iommu.c:1339: d0:PCI: map bdf = 3f:6.3
> (XEN) [VT-D]iommu.c:698: iommu_enable_translation: iommu->reg = 
> ffff82c3fff57000
> (XEN) [VT-D]iommu.c:698: iommu_enable_translation: iommu->reg = 
> ffff82c3fff56000

...

> (XEN) [VT-D]iommu.c:1468: d0:PCI: unmap bdf = 5:0.0
> (XEN) [VT-D]iommu.c:1339: d1:PCI: map bdf = 5:0.0
> (XEN) domctl.c:846:d0 XEN_DOMCTL_assign_device: assign device (5:0.0) failed


-- Pasi


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