From: Yang Zhang <yang.zhang.wz@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Steve Novakov <steve@stevenovakov.com>,
kvm@vger.kernel.org
Subject: Re: X58 Virtualization w/ Linux
Date: Mon, 20 Jun 2016 10:07:48 +0800 [thread overview]
Message-ID: <f5928924-c802-6417-a9d2-5ae171b63b6e@gmail.com> (raw)
In-Reply-To: <b918bf47-4ac1-16ab-7a4c-359d4a74c9e5@redhat.com>
On 2016/6/16 15:17, Paolo Bonzini wrote:
>
>
> On 16/06/2016 03:19, Yang Zhang wrote:
>>> intel_iommu=on
>>> intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1
>>>
>>> all sorts of combinations. I've verified that all of the relevant
>>> modules load (vfio* kvm kvm_intel pci_stub) through dmesg. That that
>>> "DMAR-IR" message is suspicious though, no? That there is some setting
>>> in the kernel that disables remapping by default for my BIOS. I've seen
>>> posts with working vt-d even with an i7-950. I wonder if they have the
>>> C3 stepping of the northbridge. Does that sound like it might be an
>>> issue?
>>>
>>> I can't believe that there is not some way to make this work, as it
>>> works flawlessly with ESXi (which sits on top of a linux kernel, though
>>> it's vmware's proprietary fork I think). If my system boots in "Plug and
>>> play" mode, the BIOS configuration for non critical devices shouldn't
>>> matter, right?
>>
>> It seems there are something wrong with vfio. Have you tried with legacy
>> device pass through? It should be disabled on new distribution(like
>> ubuntu 16.04) but RHEL6 may still support it.
>
> There shouldn't be any difference. He gets a freeze with
> intel_iommu=on, even before going to device assignment.
Yes, if system freeze on boot, then it seems something wrong in linux
kernel. Steve, can you post the dmesg log and check whether there are
some additional devices on your board? I remember some legacy device
drivers are not friendly to IOMMU.
--
best regards
yang
next prev parent reply other threads:[~2016-06-20 3:55 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
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 [this message]
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=f5928924-c802-6417-a9d2-5ae171b63b6e@gmail.com \
--to=yang.zhang.wz@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=steve@stevenovakov.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