From owner-freebsd-xen@FreeBSD.ORG Wed May 13 08:05:04 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 296C9CFC for ; Wed, 13 May 2015 08:05:04 +0000 (UTC) Received: from forward8l.mail.yandex.net (forward8l.mail.yandex.net [84.201.143.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8A611E7C for ; Wed, 13 May 2015 08:05:03 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [IPv6:2a02:6b8:0:801:1::11]) by forward8l.mail.yandex.net (Yandex) with ESMTP id 2E33B1A415C6; Wed, 13 May 2015 11:04:53 +0300 (MSK) Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id C6EF316A04A1; Wed, 13 May 2015 11:04:52 +0300 (MSK) Received: from unknown (unknown [77.66.213.135]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id JhVdnWFM5T-4qUuAgHk; Wed, 13 May 2015 11:04:52 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1431504292; bh=bNqQdIh7pVdLIxfucrG33UWf8toSMZcK5NdPuP1c+6c=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=u0+B44mFaHxR4WFtbTdsjgOU+b56z64Kcovd08UKC3OWRxy9MV3RhM3cFbep9SGFn SKifmMLFiB1FJa/6pLcIhmcn42eRH90YTaORyD/ADsJaqOoPK5UPmmrSJXrVFwsbpF p0KfK7EXDdNFtvmSESDh3blECCYJFD/u8a29cTMI= Authentication-Results: smtp12.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <55530582.2070008@yandex.ru> Date: Wed, 13 May 2015 11:04:18 +0300 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= , freebsd-xen@freebsd.org Subject: Re: iommu must be enabled for PVH hardware domain References: <55521A29.9080409@yandex.ru> <5552212D.8090308@citrix.com> In-Reply-To: <5552212D.8090308@citrix.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Wed, 13 May 2015 08:05:04 -0000 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. -- Regards, Ruslan T.O.S. Of Reality