search for: drhds

On Tue, 2015-07-28 at 10:16 +0200, Paolo Bonzini wrote: > > On 28/07/2015 03:08, Andy Lutomirski wrote: > > On Mon, Sep 1, 2014 at 10:39 AM, Andy Lutomirski <luto at amacapital.net> wrote: > >> This fixes virtio on Xen guests as well as on any other platform > >> that uses virtio_pci on which physical addresses don't match bus > >> addresses. >

On Tue, 2015-07-28 at 10:16 +0200, Paolo Bonzini wrote: > > On 28/07/2015 03:08, Andy Lutomirski wrote: > > On Mon, Sep 1, 2014 at 10:39 AM, Andy Lutomirski <luto at amacapital.net> wrote: > >> This fixes virtio on Xen guests as well as on any other platform > >> that uses virtio_pci on which physical addresses don't match bus > >> addresses. >

...ng devices > and bypassing-virtio on the same bus). Yes, for example on x86 it must be passed through the DMAR table. virtio-pci device must have a separate DRHD for them. In QEMU, you could add an "under-iommu" property to PCI bridges, and walk the hierarchy of bridges to build the DRHDs. Paolo

...sing-virtio on the same bus). > > Yes, for example on x86 it must be passed through the DMAR table. > virtio-pci device must have a separate DRHD for them. In QEMU, you > could add an "under-iommu" property to PCI bridges, and walk the > hierarchy of bridges to build the DRHDs. > > Paolo -- MST

...sing-virtio on the same bus). > > Yes, for example on x86 it must be passed through the DMAR table. > virtio-pci device must have a separate DRHD for them. In QEMU, you > could add an "under-iommu" property to PCI bridges, and walk the > hierarchy of bridges to build the DRHDs. > > Paolo -- MST

Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch Intel/Lenovo Q35 Mainboard with VT-d enabled Bootoptions iommu=1 vtd=1 pci.backhide for a PCI-E nvidia graphiccard xm dmesg Error messages includes: [VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed [VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed If i try to start my HVM by xm create