From owner-freebsd-xen@FreeBSD.ORG  Wed May 13 08:14:25 2015
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 59541E8A
 for <freebsd-xen@freebsd.org>; Wed, 13 May 2015 08:14:25 +0000 (UTC)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Cybertrust Public SureServer SV CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0EA571F9E
 for <freebsd-xen@freebsd.org>; Wed, 13 May 2015 08:14:24 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="5.13,420,1427760000"; d="scan'208";a="264541169"
Message-ID: <555307DA.2060303@citrix.com>
Date: Wed, 13 May 2015 10:14:18 +0200
From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ruslan Makhmatkhanov <cvs-src@yandex.ru>, <freebsd-xen@freebsd.org>
Subject: Re: iommu must be enabled for PVH hardware domain
References: <55521A29.9080409@yandex.ru> <5552212D.8090308@citrix.com>
 <55530582.2070008@yandex.ru>
In-Reply-To: <55530582.2070008@yandex.ru>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-DLP: MIA2
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 08:14:25 -0000

Hello,

El 13/05/15 a les 10.04, Ruslan Makhmatkhanov ha escrit:
> Roger Pau Monné wrote on 05/12/15 18:50:
>> Hello,
>>
>> El 12/05/15 a les 17.20, Ruslan Makhmatkhanov ha escrit:
>>> Hello,
>>>
>>> we have machine with VT-d and EPT-capable CPU:
>>> Intel(R) Xeon(R) CPU E5504 [1]
>>>
>>> The system is FreeBSD 11.0-CURRENT r282694 installed from
>>> ftp.freebsd.org iso.
>>>
>>> But dom0 fails to boot at this hardware with "iommu must be enabled for
>>> PVH hardware domain" [2]. VT-d support is indeed not detected at kernel
>>> level. Here is dmesg with VT-d enabled in BIOS [3] and dmesg with VT-d
>>> disabled in BIOS [4]. It's look like there is no difference on both
>>> outputs. Here is the proofpic of that the system is VT-d capable and the
>>> support is enabled in BIOS [5]. Here is acpidump -t output [6]
>>
>> My bet right now is be that Xen detects that your IOMMU contains erratas
>> and disables it. Can you add "iommu=debug,force" to your xen_cmdline and
>> try again?
>>
>> Also, can you paste the contents of your /boot/loader.conf?
>>
>> Roger.
> 
> You are right:
> 
> [VT-D] Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata #47, #53
> 
> and after that:
> 
> ----------------------------------------------
> Panic on CPU 0:
> Couldn't enable IOMMU and iommu=required/force
> ----------------------------------------------
> 
> Reboot in five seconds.
> 
> But what this means practically? Some chipset bugs preventing us to use
> this feature. Can this circumvented somehow? Thanks.

AFAIK iommu=force should force the usage of the IOMMU even if erratas
are detected. You can also try with iommu=force,no-intremap.

Roger.