Date: Sun, 30 Jan 2011 20:53:44 +1100 From: Alex <joovke@joovke.com> To: gibbs@FreeBSD.org Cc: freebsd-xen@FreeBSD.org Subject: Re: xenbusb_nop_confighook_cb timeout Message-ID: <4D453528.5000604@joovke.com> In-Reply-To: <4D4350C2.6050806@FreeBSD.org> References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <alpine.BSF.2.00.1101260859380.20212@tiktik.epipe.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D453528.5000604>