search for: intel_iommu

Hi. Im trying to set intel_iommu=on on kernel parameters at grub but for some reason it doesnt work. I edit /etc/default/grub file and i add the parameter. then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then i reboot. when i run virt-host-validate i get QEMU: Checking if IOMMU is enabled by kernel: WARN (IOMMU...

...is requires Intel VT-d, I configured the following options in the BIOS: Intel VT for Directed I/O [Enabled] Interrupt Remapping [Enabled] Coherency Support [Disabled] ATS Support [Enabled] Pass-through DMA Support [Enabled] Everything works so far, but when I add intel_iommu=on to the kernel line of my grub.conf, Dracut gives my a kernel panic while booting. I added "rdshell" to the command line and extracted the boot messages via dmesg (http://nilscaspar.ch/centos-dmesg.log). I think the main problem is this: dracut Warning: No root device "block:/dev/...

...inux kernel and initrd are specified as modules. A working grub configuration looks something like: ================================================== title measured 2.6.28.9-itpm-dirty root (hd0,3) kernel /boot/tboot.gz logging=vga,serial module /boot/vmlinuz-2.6.28.9-itpm-dirty root=/dev/sda4 ro intel_iommu=on earlyprintk=vga console=ttyS0,115200 module /boot/initrd.img-2.6.28.9-itpm-dirty module /boot/GM45_PM45_SINIT_19.BIN ================================================== I tried replicating this with a extlinux config file. ================================================== LABEL measured KER...

...or the domain? > > > > > PCI passthrough is enabled: > > > > > > [ 0.000000] Command line: > > > BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 > > > root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb > > > quiet intel_iommu=on > > > [ 0.000000] Kernel command line: > > > BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 > > > root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb > > > quiet intel_iommu=on > > > > > > And supported according dmes...

On Fri, Apr 03, 2020 at 07:37:10PM +0300, Georgios wrote: > > Hi. > Im trying to set intel_iommu=on on kernel parameters at grub but for > some reason it doesnt work. > > I edit /etc/default/grub file and i add the parameter. > > then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then i > reboot. > > when i run virt-host-validate i get > > QEMU: C...

I think i might have solve it. For some reason grub2-mkconfig doesnt work. (Have no idea why) I manage to solve it with grubby. sudo grubby --args="intel_iommu=on" --update-kernel=ALL For some reason it works. I dont know if it works if my kernel gets upgraded.

Yes dmesg | grep "EFI v" [ 0.000000] efi: EFI v2.70 by American Megatrends On Fri, 2020-04-03 at 14:29 -0400, Jonathan Billings wrote: > On Fri, Apr 03, 2020 at 07:37:10PM +0300, Georgios wrote: > > Hi. > > Im trying to set intel_iommu=on on kernel parameters at grub but > > for > > some reason it doesnt work. > > > > I edit /etc/default/grub file and i add the parameter. > > > > then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then > > i > > reboot. > > >...

On Fri, Sep 21, 2012 at 01:02:23PM +1000, John Krstev wrote: > Hi Konrad, Hey John, Please next time also include xen-devel on the To header. I''ve done that for you. > > I refer to your patch at: > http://lists.xen.org/archives/html/xen-devel/2012-01/msg01927.html > which I found reading > http://www.gossamer-threads.com/lists/xen/devel/256197 > > I have a

...9: Device initialization failed. 2015-09-06T12:41:09.726064Z qemu-kvm: -device vfio-pci,host=05:02.0,id=hostdev0,bus=pci.0,addr=0x9: Device 'vfio-pci' could not be initialized I've followed a whole load of instructions and made teh settings below: - Updated /etc/sysconfig/grub tp add intel_iommu=on: GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet intel_iommu=on" - Allowed unsafe interrupts in /etc/modprobe.d/PME-vfio_iommu_type1.conf: options vfio_iommu_type1 allow_unsafe_interrupts=1 - Blacklisted the PCI card's drivers in /etc/modprobe.d/blackli...

...ed this after adding '3' to the module line to get it to runlevel 3, but the machine came up at runlevel 5 anyway. On machines that are working correctly, the dmesg output looks like this: Command line: /boot/vmlinuz-2.6.32-642.el6.x86_64 ro root=UUID=20a8bd64-5783-4007-a5e4-e41bfc07f3c8 intel_iommu=on rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb rdblacklist=nouveau quiet if the options are on the module line or like this: Command line: ro root=UUID=7d11ff13-106f-42df-9a41-9ebf2505f6d2 rd_NO_LUKS rd_NO_LV...

Hi, This is regarding SRIOV in Rhel7. I have added intel_iommu=on in grub.cfg file. When I attach Virtual Function to VM and I try to poweron the VM, I get the below error: [root@Dell-Rhel7 ~]# virsh start rhel64x64GA error: Failed to start domain rhel64x64GA error: internal error: early end of file from monitor: possible problem: qemu-kvm: -device vfio-pci,h...

...--------------------------------- 1 file changed, 6 insertions(+), 61 deletions(-) diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c index b9f905a55dda..b906727f5b85 100644 --- a/drivers/iommu/intel-iommu.c +++ b/drivers/iommu/intel-iommu.c @@ -5781,78 +5781,27 @@ static bool intel_iommu_capable(enum iommu_cap cap) return false; } -static int intel_iommu_add_device(struct device *dev) +static struct iommu_device *intel_iommu_probe_device(struct device *dev) { - struct dmar_domain *dmar_domain; - struct iommu_domain *domain; struct intel_iommu *iommu; - struct iommu_group *g...

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

...to start domain obsdfw error: unsupported configuration: host doesn't support passthrough of host PCI devices PCI passthrough is enabled: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb quiet intel_iommu=on [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb quiet intel_iommu=on And supported according dmesg output: root at lapdev01# dmesg | grep IOM [ 0.000000] Intel-IOMMU: enabled As you...

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

...t X3 MT27500 VPI pci-express cards set up in InfiniBand mode in HP blades with Intel Xeon E5-2670 CPUs and 42GB of memory. SR-IOV is enabled in the system BIOS along with VT-X, and of course VT-d. This system is a RHEL/CENTOS 6.4 x86_64 Dom0 running a 3.9.3-1 kernel with Xen 4.1.2 installed and intel_iommu enabled in the kernel. The advantage of this kernel is the built-in mlx4_core/en/ib kernel modules which support SR-IOV added in versions 3.5 and above. The basic OFED drivers provided by Mellanox do not compile with a custom Dom0 kernel (even the 2.0-beta OFED drivers), so a 3.5 or newer linux ke...