From owner-freebsd-xen@FreeBSD.ORG Wed Apr 8 13:08:32 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 7642BB84 for ; Wed, 8 Apr 2015 13:08:32 +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" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EDE6370 for ; Wed, 8 Apr 2015 13:08:31 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.11,544,1422921600"; d="scan'208";a="253062703" Message-ID: <5525282D.8060808@citrix.com> Date: Wed, 8 Apr 2015 15:07:57 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= 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: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= Subject: Re: Fwd: Re: Unable to boot with the dom0 xen kernel References: <5523D56B.9040706@entel.upc.edu> <5523D5A7.5040809@entel.upc.edu> <5523EDBE.70709@FreeBSD.org> <5523FD07.1000707@entel.upc.edu> In-Reply-To: <5523FD07.1000707@entel.upc.edu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 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: Wed, 08 Apr 2015 13:08:32 -0000 Hello, El 07/04/15 a les 17.51, Gustau PĂ©rez ha escrit: > Removing the assert prevents the panic and thus the machine boots. > However I believe the assert was there for a reason, wouldn't it break > somewhere else? > > OTOH, I see the machine has problems handling the interruption from > all devices. I see watchdog timeouts from the mpt controller, usb, and > network. Even shutting down the machine via ACPI fails (I had to unplug > the two PS to shut it down). Probably related with the iommu=no-intremap > in the xen_cmdline, isn't it? The interrupt timeouts are probably related to the IOMMU errata, the ACPI poweroff problem is because we need to negotiate the shutdown with the hypervisor, which we currently don't do. I have a very hacky patch for FreeBSD that should fix it, but I haven't found time to properly integrate it: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c Leaving this aside, I have a patch for Xen I would like you to try on this box, it *should* fix the INS/OUTS problem (not the poweroff). I've pushed it to a branch on my git repo, you can find it at: http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1 or git://xenbits.xen.org/people/royger/xen.git branch pvh_io_ports.v1 If you still get the timeouts please post the full boot log and we can try to figure out if there's any workaround. Thanks, Roger.