Re: [vfio-users] intel skylake passthrough

Hi Nicolas, Would you be able to send the full IOMMU groups tree for both NUCs? It's nice to see for the record. I was looking at using a Broadwell or Haswell one myself. Skylake was already out of real consideration for me as I was assuming there would be the same lack of isolation as your're

Re: [vfio-users] cpu usage in guest != cpu usage in host, even with exclusive pinning

Still the same with 4.5-rc4 and AUR qemu-git. On 23 Jan 2016, at 18:55, Dan Ziemba wrote: > On Tue, 2016-01-19 at 16:52 +0100, Friedrich Oslage wrote: >> I did some more testing and it turns out to be a kernel error, >> introduced somewhere around linux 4.3. >> >> Short description of the error:

Re: [vfio-users] posted interrupts Xeon E5 v3, v4, Xeon D

Perhaps this is the answer: According to their data sheets (volume 2) both Xeon D and E5 v4 have posted_interrupts_support in vtd[0:1]_cap. E5 v3 does not. On 12 Apr 2016, at 21:51, globalgorri...@fastmail.fm wrote: Hello, Are there any differences between posted interrupt support in the

[vfio-users] posted interrupts Xeon E5 v3, v4, Xeon D

Hello, Are there any differences between posted interrupt support in the Xeon E5 v3, v4, and Xeon D? The latter two are Broadwell, but posted (external) interrupts are touted with E5 v4 while (I think) VT-d posted interrupts are already available in E5 v3. Thanks

Re: [vfio-users] fitlet I211 PCI passthrough

Even while I use SR-IOV interfaces passed through, I still find openvswitch very useful. In your scenario I might just use openvswitch and bind all the NICs. Perhaps use DPDK if you're primarily doing networking with the device. Also CoreOS might be nice if again you're building a dedicated

[vfio-users] BIOS memory mapping or chipset issue with MMIO prevents IGD pass-through in legacy mode?

Hello, Do you reckon this is what some bugzilla's find to be a motherboard memory mapping issue or a chipset issue? Any ideas on working around it besides opting the IGD out of MMIO? Doing that prevents it from being used with vfio-pci and qemu. --- i7-4790k, ASUS Z97-WS (BIOS 2403), kernel

[vfio-users] Bug exposed with Libvirt, Arch Linux and VFs with kernel 4.9+

Heads-up if you're using libvirt and Arch Linux and networking VFs and kernel 4.9+. https://bugs.archlinux.org/task/52778 ___ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users

[vfio-users] radeon vfio bus information issue?

Hi, Pass-through works fine with the the same linux 4.8 VM and nouveau and a Quadro K2200. Passing-through both a R7 260X and and a R9 290 I get the same kernel oops: IP: [] drm_pcie_get_speed_cap_mask+0x39/0xf0 [drm] More here: http://pastebin.com/Waysyk2e Both the AMD cards work fine

Re: [vfio-users] radeon vfio bus information issue?

On 24 Oct 2016, at 10:23, Alex Williamson wrote: On Mon, 24 Oct 2016 10:20:08 -0700 globalgorri...@fastmail.fm wrote: Hi, Pass-through works fine with the the same linux 4.8 VM and nouveau and a Quadro K2200. Passing-through both a R7 260X and and a R9 290 I get the same kernel oops: IP:

Re: [vfio-users] radeon vfio bus information issue?

And done. I just changed the machine type to the Q35 most recent available for me: pc-q35-2.8 The default PCIE layout worked. Up and running with Wayland on the R9 290. Thank you Alex! I hope someone else gets to enjoy a similar setup too! On 24 Oct 2016, at 10:43, Alex Williamson wrote:

Re: [vfio-users] Ryzen Primary GPU passthrough success and woes

On 4 Apr 2017, at 20:37, Daimon Wang wrote: Hi Graham,    Windows crash after switch to virtio-disk because its boot loader doesn't have driver for the disk. ^ this, and ...     Reinstall Windows with virtio-disk would fix the issue (you'll need the virtio-disk driver during installation).  

Re: [vfio-users] vfio, xeon e3s, acs, & gpus -- oh my!

On 3 Apr 2017, at 10:21, globalgorri...@fastmail.fm wrote: On 3 Apr 2017, at 10:19, Steven Walter wrote: On Mon, Apr 3, 2017 at 1:08 PM, wrote: On 2 Apr 2017, at 0:10, Joshua Hoblitt wrote: I decided to go with an E6-1650 v4 / C612 based motherboard as I

Re: [vfio-users] vfio, xeon e3s, acs, & gpus -- oh my!

On 2 Apr 2017, at 0:10, Joshua Hoblitt wrote: I decided to go with an E6-1650 v4 / C612 based motherboard as I wanted both ECC memory and a BMC. I think something this is the best option for the moment. Posted-interrupts are only on E5 v4 and Xeon-D. It makes a big difference with network

Re: [vfio-users] vfio, xeon e3s, acs, & gpus -- oh my!

On 3 Apr 2017, at 10:19, Steven Walter wrote: > On Mon, Apr 3, 2017 at 1:08 PM, wrote: >> On 2 Apr 2017, at 0:10, Joshua Hoblitt wrote: >> >>> I decided to go with an E6-1650 v4 / C612 based motherboard as I wanted >>> both ECC memory and a BMC. >> >> >> I think