From owner-freebsd-xen@FreeBSD.ORG Sun Oct 14 15:21:06 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 781AD2B8 for ; Sun, 14 Oct 2012 15:21:06 +0000 (UTC) (envelope-from egoitz@ramattack.net) Received: from proxypop03.sare.net (proxypop03.sare.net [194.30.0.207]) by mx1.freebsd.org (Postfix) with ESMTP id D86308FC12 for ; Sun, 14 Oct 2012 15:21:05 +0000 (UTC) Received: from [192.168.12.224] (unknown [212.81.198.13]) by proxypop03.sare.net (Postfix) with ESMTPSA id 1D2F89DC4B4; Sun, 14 Oct 2012 17:20:08 +0200 (CEST) Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: xenbusb_nop_confighook_cb timeout From: Egoitz Aurrekoetxea Aurre In-Reply-To: <56220767-2785-4B15-97FE-8480528939E2@ramattack.net> Date: Sun, 14 Oct 2012 17:21:03 +0200 Message-Id: <7136698E-E272-4E67-BA33-816CF9EF0B94@ramattack.net> References: <50757ADA.7060101@deployis.eu> <88AB8E8E-0D6C-4ED7-B0DC-7466DB7D3634@ramattack.net> <5075E641.20409@deployis.eu> <9512D202-F84C-435A-8E45-5E6B976733C4@ramattack.net> <56220767-2785-4B15-97FE-8480528939E2@ramattack.net> To: Mark Felder X-Mailer: Apple Mail (2.1499) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , =?iso-8859-1?Q?G=F3t_Andr=E1s?= X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Oct 2012 15:21:06 -0000 I assume this should be a Citrix bug=85. Seems like the bug :=20 Xen 4.1.1 has a bug where the emulated CDROM/DVD drive in an HVM guest = fails to work properly. This bug has been fixed in Xen 4.1.2 and later = versions. The symptoms of this bug are lost interrupts and frozen ata = commands in the kernel dmesg log. See this email thread for more = information: = http://old-list-archives.xen.org/archives/html/xen-devel/2011-10/msg02147.= html=20 documented in :=20 http://wiki.xen.org/wiki/Xen_4.1_Release_Notes does not get corrected=85 El 14/10/2012, a las 15:52, Egoitz Aurrekoetxea Aurre = escribi=F3: > Hi, >=20 > 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. >=20 > http://support.citrix.com/article/CTX132411 >=20 > And it boots=85. without modifying any source=85.=20 >=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. >=20 > Just removing it=85 you can boot properly=85.=20 >=20 > This is not the solution=85. it's just a workaround=85. >=20 > I'll try to find a solution=85. but seems here the Xen people=85 has = changed something=85. >=20 > Continue investigating=85=85 >=20 > Regards, >=20 >=20 >=20 > El 12/10/2012, a las 02:27, Egoitz Aurrekoetxea Aurre = escribi=F3: >=20 >> 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 escribi=F3: >>=20 >>> On Wed, 10 Oct 2012 16:18:57 -0500, G=F3t Andr=E1s = 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" >=20 > _______________________________________________ > 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"