From owner-freebsd-xen@FreeBSD.ORG Sat Jan 29 00:03:10 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63E7C1065672 for ; Sat, 29 Jan 2011 00:03:10 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id F3CD18FC15 for ; Sat, 29 Jan 2011 00:03:09 +0000 (UTC) Received: from [192.168.4.138] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p0SNR2pi052536 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 28 Jan 2011 16:27:03 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D4350C2.6050806@FreeBSD.org> Date: Fri, 28 Jan 2011 16:26:58 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110123 Thunderbird/3.1.8 MIME-Version: 1.0 To: Alex References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> In-Reply-To: <4D41E3D1.7040100@joovke.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Fri, 28 Jan 2011 16:27:03 -0700 (MST) Cc: freebsd-xen@FreeBSD.org Subject: Re: xenbusb_nop_confighook_cb timeout X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org 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: Sat, 29 Jan 2011 00:03:10 -0000 On 1/27/2011 2:29 PM, Alex wrote: > I've had that geom warning before on real hardware and it's never > stopped it from working. > > In my screenshot, it appears the time out is originating from: > > xenbusb.c:xenbusb_nop_confighook_cb This means that one of the PV devices is not transitioning into either the Connected or Closed state. Can you provide the output of "xenstore-ls" from your DOM0 to me privately so I can help you track this down? Thanks, Justin