[vfio-users] VFIO: DMAR kernel
MEHAN, MUNISH
mm6021 at att.com
Thu May 5 16:03:54 UTC 2016
Thanks Alex, we get this error on compute host when we run DPDK app that manages VFs. We spin the VM with following qemu and send data to this app to configure vlan filter etc on VF.
Qemu cmdline is as follows
qemu-system-x86_64 -display curses -nographic -m 2048 -hda /root/centos.raw -vga none -vnc :0 -net none -enable-kvm -device vfio-pci,host=86:10.7,id=hostdev0,bus=pci.0,addr=0x4
dmesg -T | grep -e DMAR -e IOMMU -e hardware
[Wed May 4 12:11:02 2016] ACPI: DMAR 000000007b6fe000 000118 (v01 DELL PE_SC3 00000001 DELL 00000001)
[Wed May 4 12:11:02 2016] Booting paravirtualized kernel on bare hardware
[Wed May 4 12:11:02 2016] Intel-IOMMU: enabled
[Wed May 4 12:11:02 2016] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df
[Wed May 4 12:11:02 2016] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020df
[Wed May 4 12:11:02 2016] IOAPIC id 10 under DRHD base 0xfbffc000 IOMMU 0
[Wed May 4 12:11:02 2016] IOAPIC id 8 under DRHD base 0xc7ffc000 IOMMU 1
[Wed May 4 12:11:02 2016] IOAPIC id 9 under DRHD base 0xc7ffc000 IOMMU 1
[Wed May 4 12:11:03 2016] IOMMU 0 0xfbffc000: using Queued invalidation
[Wed May 4 12:11:03 2016] IOMMU 1 0xc7ffc000: using Queued invalidation
[Wed May 4 12:11:03 2016] IOMMU: hardware identity mapping for device 0000:00:00.0
:
[Wed May 4 12:11:03 2016] IOMMU: hardware identity mapping for device 0000:86:00.0
[Wed May 4 12:11:03 2016] IOMMU: hardware identity mapping for device 0000:86:00.1
[Wed May 4 12:11:03 2016] IOMMU: hardware identity mapping for device 0000:ff:08.0
:
[Wed May 4 12:11:03 2016] IOMMU: Setting RMRR:
[Wed May 4 12:11:03 2016] IOMMU: Prepare 0-16MiB unity mapping for LPC
[Wed May 4 12:13:47 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f3521a000
[Wed May 4 12:13:47 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:49 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35219000
[Wed May 4 12:13:49 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:49 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35218000
[Wed May 4 12:13:49 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:51 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35217000
[Wed May 4 12:13:51 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:53 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35216000
[Wed May 4 12:13:53 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:55 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35215000
[Wed May 4 12:13:55 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:57 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35214000
[Wed May 4 12:13:57 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:13:59 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35213000
[Wed May 4 12:13:59 2016] DMAR:[fault reason 05] PTE Write access is not set
[Wed May 4 12:14:01 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35212000
[Wed May 4 12:14:01 2016] DMAR:[fault reason 05] PTE Write access is not set
cat /proc/meminfo
MemTotal: 263981348 kB
MemFree: 235644980 kB
Buffers: 40352 kB
Cached: 174680 kB
SwapCached: 0 kB
Active: 856268 kB
Inactive: 154508 kB
Active(anon): 802204 kB
Inactive(anon): 504 kB
Active(file): 54064 kB
Inactive(file): 154004 kB
Unevictable: 11964 kB
Mlocked: 11964 kB
SwapTotal: 4194300 kB
SwapFree: 4194300 kB
Dirty: 188 kB
Writeback: 0 kB
AnonPages: 807916 kB
Mapped: 34020 kB
Shmem: 2736 kB
Slab: 183212 kB
SReclaimable: 63456 kB
SUnreclaim: 119756 kB
KernelStack: 7448 kB
PageTables: 6332 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 123602060 kB
Committed_AS: 1264728 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 720412 kB
VmallocChunk: 34224801600 kB
HardwareCorrupted: 0 kB
AnonHugePages: 669696 kB
HugePages_Total: 16
HugePages_Free: 16
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
DirectMap4k: 218836 kB
DirectMap2M: 8071168 kB
DirectMap1G: 262144000 kB
Thanks,
Munish Mehan
On 5/5/16, 11:56 AM, "Alex Williamson" <alex.williamson at redhat.com> wrote:
>On Thu, 5 May 2016 15:40:29 +0000
>"MEHAN, MUNISH" <mm6021 at att.com> wrote:
>
>> All,
>>
>> I am trying to load a vfio driver for the Intel VFs. I am seeing the following error from kernel. I tried all the grub options with iommu=on,iommu=pt, intel_iommu=on, intel_iommu=pt,isolcpus=2,4 etc.
>>
>> Can someone suggest what can be issue here and how I can mitigate this.
>>
>> [Wed May 4 12:13:47 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f3521a000
>> [Wed May 4 12:13:47 2016] DMAR:[fault reason 05] PTE Write access is not set
>> [Wed May 4 12:13:49 2016] dear: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35219000
>> [Wed May 4 12:13:49 2016] DMAR:[fault reason 05] PTE Write access is not set
>> [Wed May 4 12:13:49 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35218000
>> [Wed May 4 12:13:49 2016] DMAR:[fault reason 05] PTE Write access is not set
>> [Wed May 4 12:13:51 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35217000
>> [Wed May 4 12:13:51 2016] DMAR:[fault reason 05] PTE Write access is not set
>> [Wed May 4 12:13:53 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35216000
>> [Wed May 4 12:13:53 2016] DMAR:[fault reason 05] PTE Write access is not set
>> [Wed May 4 12:13:55 2016] dmar: DMAR:[DMA Write] Request device [86:00.1] fault addr 1f35215000
>> [Wed May 4 12:13:55 2016] DMAR:[fault reason 05] PTE Write access is not set
>
>You get this while the VM is running? The fault address is up past
>124GB, is it safe to assume you are not running a 124GB VM? Please
>provide host dmesg booted without iommu=pt and QEMU invocation
>(available in /var/log/libvirt/qemu/ if using libvirt). Thanks,
>
>Alex
More information about the vfio-users
mailing list