From owner-freebsd-xen@FreeBSD.ORG Thu Oct 10 09:39:02 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 152067DE for ; Thu, 10 Oct 2013 09:39:02 +0000 (UTC) (envelope-from mail@shankerbalan.net) Received: from 3r6s4.syminet.com (3r6s4.syminet.com [74.80.234.42]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E298F2D13 for ; Thu, 10 Oct 2013 09:39:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shankerbalan.net; s=x; h=To:References:Message-Id:Content-Transfer-Encoding:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=eULOZWhuEcDko/Z4ov5H/ypTMKVbiZBqusPxfqwXlec=; b=LcAHhmjWJk6ANMJuBxTjxz83SHQ0uVIWjg50a7zzXtc/fIizONk0TT+rwgC4FcqHzYBVvvRp4BlHOd71oXSKoRDIpc+tuPpAEWUvlg5ecXF5s+POTll7xIdj7KTPnrEN; Received: from [103.5.132.53] (helo=buffy.local) by 3r6s4.syminet.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1VUChw-0008BA-1G for freebsd-xen@freebsd.org; Thu, 10 Oct 2013 02:39:00 -0700 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem From: Shanker Balan In-Reply-To: <849AB77F-D2E3-4BFB-B957-F9A9E53D1070@shankerbalan.net> Date: Thu, 10 Oct 2013 14:39:20 +0530 Content-Transfer-Encoding: quoted-printable Message-Id: <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> References: <1381247394.22461.31501241.11EE316E@webmail.messagingengine.com> <8F3E4CEF-75BB-4F96-8512-87B21C5AC44E@shankerbalan.net> <525509C4.9010407@citrix.com> <1381319360.6600.31880785.6E83A2F9@webmail.messagingengine.com> <52555FF4.8010107@citrix.com> <1381329411.11572.31947565.7C2A280B@webmail.messagingengine.com> <849AB77F-D2E3-4BFB-B957-F9A9E53D1070@shankerbalan.net> To: "freebsd-xen@freebsd.org" X-Mailer: Apple Mail (2.1510) X-Antiabuse: This header was added to track abuse, please include it with any abuse report X-Antiabuse: Primary Hostname - 3r6s4.syminet.com X-Antiabuse: Original Domain - freebsd.org X-Antiabuse: Originator/Caller UID/GID - [105 113] / [105 113] X-Antiabuse: Sender Address Domain - shankerbalan.net 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: Thu, 10 Oct 2013 09:39:02 -0000 On 10-Oct-2013, at 1:37 PM, Shanker Balan wrote: > On 09-Oct-2013, at 8:06 PM, Mark Felder wrote: >=20 >> On Wed, Oct 9, 2013, at 8:53, Roger Pau Monn=E9 wrote: >>> On 09/10/13 13:49, Mark Felder wrote: >>>> On Wed, Oct 9, 2013, at 2:46, Roger Pau Monn=E9 wrote: >>>>> On 09/10/13 08:18, Shanker Balan wrote: >>>>>> On 08-Oct-2013, at 9:19 PM, Mark Felder wrote: >>>>>>=20 >>>>>>> On Tue, Oct 8, 2013, at 9:45, Josias L.G wrote: >>>>>>>> Problem with Citrix Xen 6.2 and install from ISO. The = "solution" was >>>>>>>> remove cd-rom drive from virtual machine. Not possible now with = xen >>>>>>>> default in GENERIC kernel. >>>>>>>> Message error:=20 >>>>>>>> run_interrupt_driven_hooks - still waiting after 300 seconds = for >>>>>>>> xenbusb_nop_confighook_cb >>>>>>>> panic: run_interrupt_driven_config_hooks: waited too long >>>>>>>>=20 >>>>>>>=20 >>>>>>> I was going to test this soon... but you're right -- you = probably can't >>>>>>> install FreeBSD 10 from ISO on Citrix XenServer because of this = bug. >>>>>>>=20 >>>>>>> Can someone working on the xen bits test and maybe find a = workaround? >>>>>>=20 >>>>>> The "xenbusb_nop_confighook_cb" issue is the only issue which I = am aware >>>>>> of that prevents CloudStack/XenServer IaaS private clouds from = offering >>>>>> FreeBSD 10 as a supported OS template. The "vbd-destroy" = workaround is not >>>>>> possible as the ISO is attached to the VM instance during the = installation. >>>>>>=20 >>>>>> A "please pretty please" request to @citrix R&D for the hopefully = last fix >>>>>> to get FreeBSD 10 running on XenServer+CloudStack. >>>>>>=20 >>>>>> The earlier HyperV related panic on XenServer has been fixed in = ALPHA5. >>>>>=20 >>>>> Hello, >>>>>=20 >>>>> I've taken a look into this and I'm afraid there's no easy way to >>>>> workaround it from FreeBSD. When Xen is detected all IDE devices = are >>>>> disconnected, and there's no fine grained way to only disable IDE = disks >>>>> and not cdrom devices. >>>>>=20 >>>>> Could you please contact your XenServer representative, and/or = submit >>>>> this bug to xs-devel (xs-devel@lists.xenserver.org) mailing lists = in >>>>> order to get this fixed on XenServer. >>>>>=20 >>>>=20 >>>> Citrix is aware of this as I've contacted several people there and = this >>>> has been discussed both here and on the xs-devel list. There has to = be >>>> something FreeBSD can do to work around this issue since Linux and >>>> NetBSD have no issues. >>>=20 >>> Linux and NetBSD have no issues because you probably only tried them = on >>> PV mode, which doesn't exhibit this issue (also NetBSD doesn't have >>> PVHVM support, so it's quite clear it won't have this issue). >>>=20 >>>> As far as I'm aware the issue has been tracked >>>> down to badly behaving qemu in XenServer -- they don't use upstream = qemu >>>> in XenServer (yet), and instead have their own fork. A future = release is >>>> supposed to merge with upstream qemu. >>>=20 >>> The main problem here is that XenServer announces a PV block device = on >>> xenstore (the cdrom), but then it seems like there's no backend to >>> handle it, so it hangs on the connection phase. IMHO the problem is = not >>> with the device model (Qemu), but with the backend that should = handle >>> this PV device. >>>=20 >>> Xen only allows you to either disable all IDE devices or none, so = the >>> only possible solution I can think of is to not disable anything at = all >>> and use the emulated devices, which will leave us with very poor >>> performance (unless I'm missing something, there's no way to only >>> disable disks but not cdroms). >>>=20 >>>> But the fact remains that this is a non-issue on Linux and NetBSD = who >>>> handle this buggy virtual CDROM without any problems. There has to = be >>>> some way we can add a quirk on our side so this device doesn't stop = the >>>> entire boot process. If FreeBSD 10 is released without = out-of-the-box >>>> support on the premier commercial Xen platform we'll be shooting >>>> ourselves in the foot and all of this work will be for naught. = Amazon >>>> isn't the only Xen platform people use. >>>=20 >>> You can always use the pre-build VM images I guess (I have not = tested >>> those, but I expect they should work fine under Xen). >>>=20 >>> = ftp://ftp.nl.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/20131007/10.0-ALP= HA5/amd64/ >>>=20 >=20 > This is way better. Having ready to import Xen images beats ISO = installation > any day. Will try on my cloudstack setup later today. I converted the QCOV image to VHD and have imported it into CloudStack. = Instance created from the template also have the "xenbusb" issue at bootup. Oh well. Thanks for all the help. Regards. @shankerbalan