From owner-freebsd-xen@FreeBSD.ORG Tue Apr 7 11:11:29 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 D5D34EEB; Tue, 7 Apr 2015 11:11:29 +0000 (UTC) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "relay.upc.es", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 478DBE58; Tue, 7 Apr 2015 11:11:28 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id t37BBJFe012901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Tue, 7 Apr 2015 13:11:20 +0200 Received: from [10.0.2.151] ([147.83.40.10]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id t37BBJr8010799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 7 Apr 2015 13:11:19 +0200 Message-ID: <5523BB57.1010607@entel.upc.edu> Date: Tue, 07 Apr 2015 13:11:19 +0200 From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= 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==?= Subject: Re: Unable to boot with the dom0 xen kernel References: <551EFA82.9070007@entel.upc.edu> <55223D08.4040007@entel.upc.edu> <5523872E.5030700@FreeBSD.org> <5523945E.2050405@entel.upc.edu> <5523A989.4010608@FreeBSD.org> In-Reply-To: <5523A989.4010608@FreeBSD.org> X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.4.3 (dash.upc.es [147.83.2.50]); Tue, 07 Apr 2015 13:11:20 +0200 (CEST) X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.4.3 (ackerman2.upc.es [147.83.2.244]); Tue, 07 Apr 2015 13:11:19 +0200 (CEST) X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 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, 07 Apr 2015 11:11:30 -0000 Hi Roger, >>> If you don't have a serial console you >>> should use console=vga in your xen_cmdline. Additionally if you have a >>> usb debug port you could use that as console with console=dbgp [1]. >> Thank you. I did not have a console at $home (the laptop has no >> physical serial port) but at $work my laptop dockstation provides me >> with a physical serial port. I'll try to use it. Well, my current laptop (Dell latitude E6430) and the previous one (Fujitsu Lifebook) have that. I'd say that even an old D630 laptop had that option. It is quite useful. > I didn't know there were dock stations that provided serial ports even > when the laptop didn't have them, that's something worth a try. If not > just setting console=vga ought to provide some output. If that also > fails please write back and I will provide a patch for the bootloader in > order to try to figure out what's going on. > > Roger. I added a new test machine. I'll show my results with this one (I'll report my laptop results later). The new machine is Intel(R) Xeon(R) CPU L5520 @ 2.27GHz EPT and IOMMU are there: [root@hast16 ~/xen]# dmesg|grep EPT VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID [root@hast16 ~/xen]# acpidump -t | grep DMAR DMAR: Length=432, Revision=1, Checksum=213, First I tried xen and xen-tools from ports (version 4.5, hoping those were enought). The boot failed, he error says iommu is not enabled. The complete log is here: http://dpaste.com/0KCGGW7 so I switched to git version instead. The error was the same. I suspect this is the reason: (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata #47, #53 According to the article [1] it is possible to prevent interruption remapping. I added iommu=no-intremap (it is listed in [2]), it appears the xen kernel is happy with that, but then the domain0 FreeBSD kernel panics: http://dpaste.com/3TJYYDQ Gustau [1] http://support.citrix.com/article/CTX136517 [2] http://xenbits.xenproject.org/docs/unstable/misc/xen-command-line.html PS: I'd like to talk about the behavior of the xen_cmdline reboot option. Setting it "no" causes the machine to stop (which is fine) but the machine remains there. Perhaps it'd be good to allow to reboot the machine by pressing a key when in panic. Otherwise you have physically reboot the machine. -- --------------------------------------------------------------------------- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona