From: Paolo Bonzini <pbonzini@redhat.com>
To: Steve Novakov <steve@stevenovakov.com>,
Yang Zhang <yang.zhang.wz@gmail.com>,
kvm@vger.kernel.org
Subject: Re: X58 Virtualization w/ Linux
Date: Wed, 15 Jun 2016 08:59:07 +0200 [thread overview]
Message-ID: <c1558e01-83ef-86f2-0c4a-68308853eb55@redhat.com> (raw)
In-Reply-To: <cdd1092f-5b13-b8fc-707a-8f2596f4f7f8@stevenovakov.com>
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
next prev parent reply other threads:[~2016-06-15 6:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 21:34 X58 Virtualization w/ Linux Steve Novakov
2016-06-12 1:46 ` Yang Zhang
2016-06-12 1:55 ` Steve Novakov
2016-06-12 2:54 ` Steve Novakov
2016-06-12 2:57 ` Steve Novakov
2016-06-13 1:46 ` Yang Zhang
2016-06-13 3:32 ` Steve Novakov
2016-06-13 20:11 ` Steve Novakov
2016-06-14 22:00 ` Steve Novakov
2016-06-15 5:04 ` Steve Novakov
2016-06-15 6:59 ` Paolo Bonzini [this message]
2016-06-15 15:40 ` Steve Novakov
2016-06-16 1:19 ` Yang Zhang
2016-06-16 1:22 ` Steve Novakov
2016-06-16 7:17 ` Paolo Bonzini
2016-06-20 2:07 ` Yang Zhang
2016-06-20 4:05 ` Steve Novakov
[not found] ` <97e6a96d-4139-2469-a8c9-f79df48727a6@stevenovakov.com>
2016-06-21 1:21 ` Yang Zhang
2016-06-21 1:24 ` Steve Novakov
2016-06-27 2:21 ` Yang Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1558e01-83ef-86f2-0c4a-68308853eb55@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=steve@stevenovakov.com \
--cc=yang.zhang.wz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox