From owner-freebsd-xen@FreeBSD.ORG Tue May 12 15:51:19 2015 Return-Path: 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 0012D465 for ; Tue, 12 May 2015 15:51:18 +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 A9A7C1EFE for ; Tue, 12 May 2015 15:51:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,415,1427760000"; d="scan'208";a="264266635" Message-ID: <5552212D.8090308@citrix.com> Date: Tue, 12 May 2015 17:50:05 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= 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 , Subject: Re: iommu must be enabled for PVH hardware domain References: <55521A29.9080409@yandex.ru> In-Reply-To: <55521A29.9080409@yandex.ru> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2015 15:51:19 -0000 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.