From owner-freebsd-xen@FreeBSD.ORG Tue May 12 15:20:47 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 6BB2DB6A for ; Tue, 12 May 2015 15:20:47 +0000 (UTC) Received: from forward6l.mail.yandex.net (forward6l.mail.yandex.net [IPv6:2a02:6b8:0:1819::6]) (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 299091B0D for ; Tue, 12 May 2015 15:20:46 +0000 (UTC) Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net [IPv6:2a02:6b8:0:f05::116]) by forward6l.mail.yandex.net (Yandex) with ESMTP id AD07414E0DAE for ; Tue, 12 May 2015 18:20:43 +0300 (MSK) Received: from smtp2h.mail.yandex.net (localhost [127.0.0.1]) by smtp2h.mail.yandex.net (Yandex) with ESMTP id 517FE1703F9D for ; Tue, 12 May 2015 18:20:43 +0300 (MSK) Received: from unknown (unknown [77.66.213.135]) by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id VBpBwTTmPM-KgWaNOHD; Tue, 12 May 2015 18:20:42 +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=1431444042; bh=EhYF9s6xO4lBhxrNpj5bkUEDAdvqKviXiki9gasSzVI=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: Content-Type:Content-Transfer-Encoding; b=YvtWoLvsKZ2w2D27K/QKHOdjUFYfA8rXMLXd//cutWy8sgOTChh9tY8o/vmY/m/5k LFUS0ivRH7ljw5miPYCFJe8VcL4PG2q49pzTKjvruDkiWVj0+JlD0T0sKO1/xh4gj3 86O7aIT+JJLWhH+gSOenGtW9BfWylLI1CIlVlnV8= Authentication-Results: smtp2h.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <55521A29.9080409@yandex.ru> Date: Tue, 12 May 2015 18:20:09 +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: freebsd-xen@freebsd.org Subject: iommu must be enabled for PVH hardware domain Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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:20:47 -0000 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] Any suggestions what may be wrong? Thanks. [1] http://ark.intel.com/products/40711/Intel-Xeon-Processor-E5504-4M-Cache-2_00-GHz-4_80-GTs-Intel-QPI [2] https://people.freebsd.org/~rm/vt-d_on_proliant/dom0_fails_to_boot.mov [3] https://people.freebsd.org/~rm/vt-d_on_proliant/vt-d_enabled_in_bios.txt [4] https://people.freebsd.org/~rm/vt-d_on_proliant/vt-d_disabled_in_bios.txt [5] https://people.freebsd.org/~rm/vt-d_on_proliant/there_is_vt-d_option_in_vios.jpg [6] https://people.freebsd.org/~rm/vt-d_on_proliant/acpidump-t.txt -- Regards, Ruslan T.O.S. Of Reality