From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 09:53:48 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 EBDC1106564A for ; Sun, 30 Jan 2011 09:53:48 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD8E8FC13 for ; Sun, 30 Jan 2011 09:53:47 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0U9riOw016230; Sun, 30 Jan 2011 20:53:45 +1100 Message-ID: <4D453528.5000604@joovke.com> Date: Sun, 30 Jan 2011 20:53:44 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: gibbs@FreeBSD.org 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> <4D4350C2.6050806@FreeBSD.org> In-Reply-To: <4D4350C2.6050806@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 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: Sun, 30 Jan 2011 09:53:49 -0000 Hi Justin, I am using FreeBSD as the OS on a VPS (Xen HVM). Do you think the VPS provider will provide that information without too much drama? On 29/01/11 10:26, Justin T. Gibbs wrote: > 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 >