From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: chris <tknchris@gmail.com>
Cc: Xen-Devel List <xen-devel@lists.xensource.com>,
Xen-Users List <xen-users@lists.xensource.com>
Subject: Re: [Xen-users] VTD not working on Intel DX58SO w/ Xen 4.0.1
Date: Mon, 29 Nov 2010 22:28:16 +0200 [thread overview]
Message-ID: <20101129202816.GZ2754@reaktio.net> (raw)
In-Reply-To: <AANLkTik2MQAc-0E=EAZsA0xY=YrtFSrt9ZGhZRe20-uL@mail.gmail.com>
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@iki.fi> 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@debian.org) (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
next prev parent reply other threads:[~2010-11-29 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 16:13 VTD not working on Intel DX58SO w/ Xen 4.0.1 chris
2010-11-29 17:13 ` Konrad Rzeszutek Wilk
2010-11-29 17:31 ` alarson
2010-11-29 17:39 ` chris
2010-11-29 17:46 ` Re: [Xen-devel] " Mike Viau
2010-11-29 18:42 ` [Xen-users] " Pasi Kärkkäinen
2010-11-29 19:48 ` chris
2010-11-29 20:01 ` Mike Viau
2010-11-29 20:06 ` chris
2010-11-29 20:28 ` Pasi Kärkkäinen [this message]
2010-11-30 8:31 ` Jan Beulich
2010-12-02 15:25 ` [Xen-devel] " chris
2010-12-07 18:46 ` chris
2011-01-22 3:52 ` chris
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=20101129202816.GZ2754@reaktio.net \
--to=pasik@iki.fi \
--cc=tknchris@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.