Date: Sun, 14 Oct 2012 15:52:32 +0200 From: Egoitz Aurrekoetxea Aurre <egoitz@ramattack.net> To: Mark Felder <feld@feld.me> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org>, =?windows-1252?Q?G=F3t_Andr=E1s?= <got.andras@deployis.eu> Subject: Re: xenbusb_nop_confighook_cb timeout Message-ID: <56220767-2785-4B15-97FE-8480528939E2@ramattack.net> In-Reply-To: <9512D202-F84C-435A-8E45-5E6B976733C4@ramattack.net> References: <50757ADA.7060101@deployis.eu> <88AB8E8E-0D6C-4ED7-B0DC-7466DB7D3634@ramattack.net> <F826C6FD-AE9C-46A5-9029-85D79B1B937C@ramattack.net> <op.wly779dz34t2sn@tech304> <E8FB52A5-FCB8-4773-814A-72D4F44B03F2@ramattack.net> <5075E641.20409@deployis.eu> <op.wl05jeqn34t2sn@tech304> <9512D202-F84C-435A-8E45-5E6B976733C4@ramattack.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I get finally a decent workaround. Xen 4.1.3 serves the cdrom in a way = that seems not to like to FreeBSD. The workaround is basically remove = the cd drive between offered devices to the vm=85. Just to follow this = on xcp/xenserver=85. http://support.citrix.com/article/CTX132411 And it boots=85. without modifying any source=85.=20 First time I debugged probably did something wrong and didn't see the = printfs set by me to print any variable %s content=85 later yes=85. was = "intr config"=85.. and the boot proccess was stopped here=85 it stops = always in the cd initialization part=85. it's not able to make the cd to = come online=85. Just removing it=85 you can boot properly=85.=20 This is not the solution=85. it's just a workaround=85. I'll try to find a solution=85. but seems here the Xen people=85 has = changed something=85. Continue investigating=85=85 Regards, El 12/10/2012, a las 02:27, Egoitz Aurrekoetxea Aurre = <egoitz@ramattack.net> escribi=F3: > Hi Mark, >=20 > I assume are better (and fur more safer) ways... Seems some Xen pv = specific device has some issue being "attached"... I'm debuging it to = see which device is the one is causing the problem.... Then I could = (depending on the device) avoid attaching it or try to see how to handle = it properly... >=20 > Regards, >=20 > Egoirz Aurrekoetxea Aurre > egoitz@ramattack.net >=20 > El 11/10/2012, a las 21:53, Mark Felder <feld@feld.me> escribi=F3: >=20 >> On Wed, 10 Oct 2012 16:18:57 -0500, G=F3t Andr=E1s = <got.andras@deployis.eu> wrote: >>=20 >>> The patched worked for me also. I hope somehow it'll make to into = 9.1rc if send a reply to the previous PR. >>=20 >> Can we get a confirmation from any devs about whether or not this = patch is the "right way" to fix it? If so, I'd also appreciate seeing = this slip into 9.1 so the latest stable FreeBSD release works reliably = with the latest stable XenServer/XCP release... >> _______________________________________________ >> 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?56220767-2785-4B15-97FE-8480528939E2>