From owner-freebsd-xen@FreeBSD.ORG Tue May 12 16:35:42 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 317A6FAB for ; Tue, 12 May 2015 16:35:42 +0000 (UTC) Received: from forward10l.mail.yandex.net (forward10l.mail.yandex.net [IPv6:2a02:6b8:0:1819::a]) (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 E4C05156E for ; Tue, 12 May 2015 16:35:41 +0000 (UTC) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [37.140.190.26]) by forward10l.mail.yandex.net (Yandex) with ESMTP id 201E7BA0E96; Tue, 12 May 2015 19:35:30 +0300 (MSK) Received: from smtp1o.mail.yandex.net (localhost [127.0.0.1]) by smtp1o.mail.yandex.net (Yandex) with ESMTP id 9245ADE0041; Tue, 12 May 2015 19:35:29 +0300 (MSK) Received: from unknown (unknown [77.66.213.135]) by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id lIABjlObdW-ZS6Kq9bR; Tue, 12 May 2015 19:35:29 +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=1431448529; bh=74PVhpPt6ENleQJplzQ897yfqhIuiovb1mLghtn5sw8=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=HTQCyyAAMIVNqJIS6MMwki2+VsxGea6oQYFu4xQYRaYRk3Rr7ifkIWtw3moRWbwNu VBClO4fxEwbCVe2Af7MyWv2ssVjwqZu9b6EZjKQrLFxgPNuMDvdE9fKI2G23GOay97 JpxFujtsUgKcarUfDqSz5iilRPY6tViNFllUK4xI= Authentication-Results: smtp1o.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <55522BAF.1030209@yandex.ru> Date: Tue, 12 May 2015 19:34:55 +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: Tue, 12 May 2015 16:35:42 -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. Sorry, I can only test iommu debug option tomorrow, so will send it's output later. /boot/loader.conf contents below: rm@:~ % cat /boot/loader.conf zfs_load="YES" vfs.root.mountfrom="zfs:storage/root" xen_kernel="/boot/xen" xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 guest_loglvl=all loglvl=all" -- Regards, Ruslan T.O.S. Of Reality