From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: X58 Virtualization w/ Linux Date: Wed, 15 Jun 2016 08:59:07 +0200 Message-ID: References: <03f27bbf-f8ad-b377-c194-adaefe808077@stevenovakov.com> <2884c8b8-9ad3-cba7-d9ba-b94946775087@gmail.com> <0cc56e39-829c-144d-5e30-7d5505fe896a@stevenovakov.com> <3b5e8af3-c0da-8fab-8f40-05fa27ef2866@stevenovakov.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Steve Novakov , Yang Zhang , kvm@vger.kernel.org Return-path: Received: from mail-wm0-f53.google.com ([74.125.82.53]:36938 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750841AbcFOG7L (ORCPT ); Wed, 15 Jun 2016 02:59:11 -0400 Received: by mail-wm0-f53.google.com with SMTP id a66so9137984wme.0 for ; Tue, 14 Jun 2016 23:59:11 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 15/06/2016 07:04, Steve Novakov wrote: > So I swapped over to ubuntu 16.04 server and I just saw this line in dmesg: > > [0.100541] DMAR-IR: This system BIOS has enabled interrupt remapping on > a chipset that contains an erratum making that feature unstable. To > maintain system stability interrupt remapping is being disabled.please > contact your BIOS vendor for an update. > > This line was actually present while using arch as well I just never > took the time to read past the first line (which just says enabled > interrupt remapping). This seems to be an issue with northbridge > stepping B3, and was apparently fixed in stepping C2 ( I have B3 : ( ). > > I wonder if it's even possible to get this to work with my motherboard > now....**though ESXi can manage just fine...** > > Maybe there's some way to trick linux into just trying to do it. I mean, > it seems to pass devices to pci-stub just fine. Passing devices to pci-stub doesn't require the IOMMU, it's just swapping the driver that binds to the device. I think this is why with VT-d disabled you cannot assign the device to vfio-pci. Does it still freeze with Ubuntu 16.04 (VT-d enabled, vfio_iommu_type1.allow_unsafe_interrupts=1)? Thanks, Paolo