Re: [vfio-users] intel_iommu=on breaks audio on haswell cpu

2016-05-23 Thread Le anonymous faker
"intel_iommu=on,igfx_off" means that HDMI audio output will work but PCI passthrough won't. I already tried this, with lots of outputs: https://bbs.archlinux.org/viewtopic.php?id=204460 Thanks ! 2016-05-21 19:09 GMT+02:00 Colin Godsey : > intel_iommu=on,igfx_off should work > > On Sat, May

Re: [vfio-users] Recommendation for LGA2011 board

2016-05-23 Thread Bronek Kozicki
On 23/05/2016 19:20, Brian Yglesias wrote: I have another thread whereby I try and fail to get vfio/VT-d working on two separate lga1366 boards. (Asus Rampage II Gene and GA-EX58-UD5; both due to broken BIOS). I was considering a rampage III, also 1366/X58, which is reported to work, or an

Re: [vfio-users] Recommendation for LGA2011 board

2016-05-23 Thread Brandon Ganem
Haven't had issues with: http://www.asrock.com/mb/Intel/X99%20Extreme4/ Using ECC memory with a XEON right now. No issues On Mon, May 23, 2016 at 1:17 PM, A de Beus wrote: > The Rampage IV Extreme is what I use, there are multiple success stories > with it. > > On May 23, 2016, at 11:20 AM, Bri

Re: [vfio-users] Recommendation for LGA2011 board

2016-05-23 Thread A de Beus
The Rampage IV Extreme is what I use, there are multiple success stories with it. > On May 23, 2016, at 11:20 AM, Brian Yglesias > wrote: > > I have another thread whereby I try and fail to get vfio/VT-d working on two > separate lga1366 boards. (Asus Rampage II Gene and GA-EX58-UD5; both du

[vfio-users] Recommendation for LGA2011 board

2016-05-23 Thread Brian Yglesias
I have another thread whereby I try and fail to get vfio/VT-d working on two separate lga1366 boards.  (Asus Rampage II Gene and GA-EX58-UD5; both due to broken BIOS). I was considering a rampage III, also 1366/X58, which is reported to work, or an OEM system, bug given some of the issues with X58,

Re: [vfio-users] Passing intel_iommu=on in grub causes boot to immediately lock on two different X58 LGA1366 MB.

2016-05-23 Thread Alex Williamson
On Mon, May 23, 2016 at 3:20 AM, Brian Yglesias < br...@atlanticdigitalsolutions.com> wrote: > Sorry for the schizophrenic posts. > > Updating the BIOS reset it to default, which returned VT-d to the default > setting of 'disabled', and that is the only reason I was able to boot. > > I tried the n

Re: [vfio-users] VFIO and random host crashes

2016-05-23 Thread Colin Godsey
I’m now 98% certain I was seeing the ‘skylake freeze’, or one of the other random bugs in the skylake microcode. Updated to the newest BIOS and everything is rock solid (my old one was only 5 months old). There were two big issues regarding c-states and ‘complex workloads’ that would result in a C

Re: [vfio-users] Passing intel_iommu=on in grub causes boot to immediately lock on two different X58 LGA1366 MB.

2016-05-23 Thread Brian Yglesias
Sorry for the schizophrenic posts. Updating the BIOS reset it to default, which returned VT-d to the default setting of 'disabled', and that is the only reason I was able to boot. I tried the new card in both motherboards, and the result is the same. So, just to update my previous response:  VT-d r

Re: [vfio-users] Passing intel_iommu=on in grub causes boot to immediately lock on two different X58 LGA1366 MB.

2016-05-23 Thread Brian Yglesias
In a spectacular oversight on my part, I did not update the Asus Rampage II Gene's BIOS to the most recent, as I thought I had. In addition, I had purchased a cheap GPU (EVGA GT 730), and when I put it in the board, it booted up normally, and dmesg shows IOMMU and DMAR working. There is a lot of ne