[dpdk-dev] DMAR fault

ystem-x86_64: -device pci-assign,host=03:10.0: Device > 'kvm-pci-assign' could not be initialized > > The device is detached from kernel, and move to pci-stub. dmesg does not > show any DMAR fault message anymore. > > Any idea? > > Jinho > > > Jinho, > you need to specify both > > " intel_iommu=on iommu=pt" > > Pb > I tried that as well, but it works as if I only add intel_iommu=on.. which means I do not receive any packets from hypervisor. I also have pci realloc added. Does this affect? Jinho -- next part -- An HTML attachment was scrubbed... URL: <http://dpdk.org/ml/archives/dev/attachments/20130812/dca6585a/attachment.html>

[dpdk-dev] DMAR fault

10.0: Device > initialization failed. > qemu-system-x86_64: -device pci-assign,host=03:10.0: Device > 'kvm-pci-assign' could not be initialized > > The device is detached from kernel, and move to pci-stub. dmesg does > not show any DMAR fault message anymore. > > Any idea? > > Jinho Jinho, you need to specify both " intel_iommu=on iommu=pt" Pb -- next part -- An HTML attachment was scrubbed... URL: <http://dpdk.org/ml/archives/dev/attachments/20130812/2a63772e/attachment.html>

[dpdk-dev] DMAR fault

o assign device "(null)" qemu-system-x86_64: -device pci-assign,host=03:10.0: Device initialization failed. qemu-system-x86_64: -device pci-assign,host=03:10.0: Device 'kvm-pci-assign' could not be initialized The device is detached from kernel, and move to pci-stub. dmesg does not show any DMAR fault message anymore. Any idea? Jinho -- next part -- An HTML attachment was scrubbed... URL: <http://dpdk.org/ml/archives/dev/attachments/20130812/28f347ff/attachment.html>

[dpdk-dev] DMAR fault

IOS. I am currently using BIOS version 3.0, > but the latest is 6.3.0. Does this affect the matter? > > Any help appreciated! > > Jinho > -- next part -- An HTML attachment was scrubbed... URL: <http://dpdk.org/ml/archives/dev/attachments/20130812/4226122c/attachment.html>