From owner-freebsd-xen@FreeBSD.ORG  Thu Dec  4 08:46:52 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B959D30E
 for <freebsd-xen@freebsd.org>; Thu,  4 Dec 2014 08:46:52 +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" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 16254EA3
 for <freebsd-xen@freebsd.org>; Thu,  4 Dec 2014 08:46:51 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="5.07,514,1413244800"; d="scan'208";a="199898544"
Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com
 (10.13.107.79) with Microsoft SMTP Server id 14.3.181.6; Thu, 4 Dec 2014
 03:46:47 -0500
Message-ID: <54801F77.5050700@citrix.com>
Date: Thu, 4 Dec 2014 09:46:47 +0100
From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "David P. Discher" <dpd@dpdtech.com>
Subject: Re: Attempting to Get Xen FreeBSD Dom0 working
References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com>
 <547DFCC0.6030003@citrix.com>
 <DCB954B5-0E45-4DE6-AAC4-C5ACF7FD90A7@dpdtech.com>
 <547F1476.8080305@citrix.com>
 <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com>
 <547F59B4.1010105@citrix.com>
 <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com>
 <547F6AC1.9060709@citrix.com>
 <BBBFE7EC-BB42-4514-9A68-437ECAB8E640@dpdtech.com>
 <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com>
In-Reply-To: <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com>
Content-Type: text/plain; charset="windows-1252"
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 08:46:52 -0000

Hello,

El 04/12/14 a les 3.27, David P. Discher ha escrit:
> So, the “working” part … the hypervisor up, and Dom0 running, is correct.
> 
> However, after ~5 minutes, the AHCI buses timeout.  This seems to be constantly 
> reproducible via Dom0.  FreeBSD on the this bare metal does’t have this issue.

If you boot Xen with iommu=debug, do you see any messages on the Xen
console?

My test boxes also use AHCI, but the chipset is not exactly the same
(mine is ICH8, yours is ICH10). Do you do anything specific to trigger
the timeout, or just leaving Dom0 in an idle state also triggers this?

Could you switch to the Xen console and post the output of the "i" debug
key when this happens?

Also, you can try to play with the AHCI driver sysctls, to see if some
of them have any effect. I would recommend trying to disable MSI
interrupts (hint.ahci.X.msi=0) and power control (hint.ahcich.X.pm_level=0).

Roger.