Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Jan 2011 22:27:07 +1100
From:      Alex <joovke@joovke.com>
To:        freebsd-xen@freebsd.org
Subject:   Re: xenbusb_nop_confighook_cb timeout
Message-ID:  <4D454B0B.1030208@joovke.com>
In-Reply-To: <4D41E3D1.7040100@joovke.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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"
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D454B0B.1030208>