[cc +vfio-users]
On Thu, 16 Aug 2018 19:50:04 +0200
Jes Urup wrote:
> I still get the same error.
> But i managed to get this from dmesg:
> https://paste.pound-python.org/show/lZ7ZsSrZn7pmfekxI6hU/
> Could it be bacause of grsec/pax ?
Potentially, I don't have any experience with either of thos
[cc +vfio-users]
On Thu, 16 Aug 2018 18:39:18 +0200
Jes Urup wrote:
> Okay, i thought that i should add a network card to the vm and select the
> physical nic.
> So i now tried to add the physical nic from "PCI Host Device", but i then
> get this error when i try to start it: :04:00.0: no su
[cc +vfio-users]
On Wed, 15 Aug 2018 20:14:29 +0200
Jes Urup wrote:
> Yes i enabled that in /etc/default/grub cmdline. I have this: iommu=on
> intel_iommu=on hugepages=1024
> When i run that command i get this:
> https://paste.pound-python.org/show/8FrWghxbcz8qWYdAh8wl/
>
> I want :03:00.0
On Wed, 15 Aug 2018 19:48:21 +0200
Jes Urup wrote:
> Hello,
> Im really having some trouble getting iommu/vfio-pci to work.
> Im running on a supermicro X8SIE-F. I have enabled vt-d in bios.
> I used dpdk-devbind so it uses vfio-pci driver, but the kernel module is
> still e1000e.
> I've added mo
On 2018-08-15 19:48, Jes Urup wrote:
Hello,
Im really having some trouble getting iommu/vfio-pci to work.
Im running on a supermicro X8SIE-F. I have enabled vt-d in bios.
I used dpdk-devbind so it uses vfio-pci driver, but the kernel module is
still e1000e.
I've added modules="vfio vfio-pci vfio_
