From owner-freebsd-xen@FreeBSD.ORG Sun Jan 30 11:27: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 DD968106566B for ; Sun, 30 Jan 2011 11:27:10 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id 6F30A8FC08 for ; Sun, 30 Jan 2011 11:27:10 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0UBR7GA008299 for ; Sun, 30 Jan 2011 22:27:08 +1100 Message-ID: <4D454B0B.1030208@joovke.com> Date: Sun, 30 Jan 2011 22:27:07 +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: freebsd-xen@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> In-Reply-To: <4D41E3D1.7040100@joovke.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 11:27:10 -0000 This problem seems to have disappeared, the only thing i have done in the config at my VPS provider was mount a cdrom image.. On 28/01/11 08:29, 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 > > xenbusb_nop_confighook_cb(void *arg __unused) > { > } > > called in xenbusb_attach(device_t dev, char *bus_node, u_int > id_components) > > /* > * Since XenBus busses are attached to the XenStore, and > * the XenStore does not probe children until after interrupt > * services are available, this config hook is used solely > * to ensure that the remainder of the boot process (e.g. > * mount root) is deferred until child devices are adequately > * probed. We unblock the boot process as soon as the > * connecting child count in our softc goes to 0. > */ > xbs->xbs_attach_ch.ich_func = xenbusb_nop_confighook_cb; > > > Regarding the partitioning, I am not sure what you mean. I have this > configured as a VPS so I want to avoid doing anything that may destroy > data on the disk. > > > > On 28/01/11 06:29, Nick Sayer wrote: >> On Jan 27, 2011, at 1:43 AM, Alex wrote: >> >>> I've applied this patch, I now get past the ethernet issue, and have >>> run into another problem, see screenshot: >>> >>> http://ahhyes.net/xen1.jpg >>> >>> any ideas? >>> >> The disk geometry differs from the PV device and the emulated >> hardware, I suspect. >> >> I was using GPT when I migrated, so I suspect that the issue was >> moot. What is your partitioning schema for this disk? Can you switch >> over to GPT... uh... >> somehow?_______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >