From owner-freebsd-xen@FreeBSD.ORG Sun Oct 13 02:48:35 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 A3EE312E for ; Sun, 13 Oct 2013 02:48:35 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 64C2A2C9A for ; Sun, 13 Oct 2013 02:48:34 +0000 (UTC) Received: from [192.168.0.99] (macbook.scsiguy.com [192.168.0.99]) (authenticated bits=0) by aslan.scsiguy.com (8.14.7/8.14.5) with ESMTP id r9D2mXT6040559 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 12 Oct 2013 20:48:33 -0600 (MDT) (envelope-from gibbs@scsiguy.com) 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: "Justin T. Gibbs" In-Reply-To: <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> Date: Sat, 12 Oct 2013 20:48:33 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> To: Shanker Balan X-Mailer: Apple Mail (2.1510) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (aslan.scsiguy.com [70.89.174.89]); Sat, 12 Oct 2013 20:48:33 -0600 (MDT) Cc: "freebsd-xen@freebsd.org" 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, 13 Oct 2013 02:48:35 -0000 On Oct 10, 2013, at 3:09 AM, Shanker Balan = wrote: >=20 > On 10-Oct-2013, at 1:37 PM, Shanker Balan = wrote: >=20 >> 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. >=20 > 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. >=20 > Oh well. >=20 > Thanks for all the help. >=20 > Regards. > @shankerbalan The CDROM issue should be resolved in FreeBSD/head. These fixes will be = include in 10.0-BETA2 as well as the first 11-CURRENT snapshot that should pop = up in the next day or two. The snapshots are announced on the = freebsd-snapshots mailing list. -- Justin From owner-freebsd-xen@FreeBSD.ORG Sun Oct 13 04:14:40 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A3FE4FF1 for ; Sun, 13 Oct 2013 04:14:40 +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 6B6D220B8 for ; Sun, 13 Oct 2013 04:14:40 +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=a3b0ey5A2w0H8OPevUadZE8Lu+5bjUDsRK2mKZqPM1Y=; b=SglyOs6ZnddOFhc9wA5o45B/dGkdWiDonmtQHkG4oGr234X0Kttp5gjUSRPdqiBF6uTLSq1YepJ9wr6q9K4ytjUzAH/ukkTIo8cxUMPTXiFoEcscG78HBhedc/vDA/8C; 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 1VVD4b-0005pl-0v for freebsd-xen@freebsd.org; Sat, 12 Oct 2013 21:14:33 -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: Date: Sun, 13 Oct 2013 09:44:30 +0530 Content-Transfer-Encoding: quoted-printable Message-Id: <517F7199-BF75-42FA-807E-76DEB49ADC6B@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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@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: Sun, 13 Oct 2013 04:14:40 -0000 On 13-Oct-2013, at 8:18 AM, Justin T. Gibbs wrote: > On Oct 10, 2013, at 3:09 AM, Shanker Balan = wrote: >=20 >>=20 >> On 10-Oct-2013, at 1:37 PM, Shanker Balan = wrote: >>=20 >>> 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. >>=20 >> 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. >>=20 >> Oh well. >>=20 >> Thanks for all the help. >>=20 >> Regards. >> @shankerbalan >=20 > The CDROM issue should be resolved in FreeBSD/head. These fixes will = be include > in 10.0-BETA2 as well as the first 11-CURRENT snapshot that should pop = up in > the next day or two. The snapshots are announced on the = freebsd-snapshots > mailing list. I just saw the commit myself. Really looking forward to FreeBSD 10 on = XenServers.=20 Thank you very much much. Regards. @shankerbalan From owner-freebsd-xen@FreeBSD.ORG Sun Oct 13 14:58:44 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 63E1C559 for ; Sun, 13 Oct 2013 14:58:44 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3098226C4 for ; Sun, 13 Oct 2013 14:58:43 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B28F12112F for ; Sun, 13 Oct 2013 10:58:42 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Sun, 13 Oct 2013 10:58:42 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=6GbpC5RwhpbLNQUdQb8V4vnhdOA=; b=hgI ZARRbWJ3kqCMnGuNHgPE3x8XN1GvAKXIGUHmMfYMBXsU/2TUE9PBVIlVZbndstiT PSooQ27zpAXskNW1Ct+OiSut5aR33yWqNpUsbecrnEOrtaoTJSMaqjinuzqSRqXF aCPSeVQIR/MrfCwHWUE8/7AycZGRc3ZtZK7/mNAc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 89D5D119632; Sun, 13 Oct 2013 10:58:42 -0400 (EDT) Message-Id: <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> X-Sasl-Enc: E1kGC6Jc6KyRS8zC2kMHVdPOkAdgTe8JkFiDLS6llz/t 1381676322 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem Date: Sun, 13 Oct 2013 09:58:42 -0500 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, 13 Oct 2013 14:58:44 -0000 On Sat, Oct 12, 2013, at 21:48, Justin T. Gibbs wrote: > On Oct 10, 2013, at 3:09 AM, Shanker Balan wrote: >=20 > >=20 > > On 10-Oct-2013, at 1:37 PM, Shanker Balan wrote: > >=20 > >> 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 probabl= y 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 workar= ound? > >>>>>>>=20 > >>>>>>> The "xenbusb_nop_confighook_cb" issue is the only issue which I a= m aware > >>>>>>> of that prevents CloudStack/XenServer IaaS private clouds from of= fering > >>>>>>> FreeBSD 10 as a supported OS template. The "vbd-destroy" workarou= nd is not > >>>>>>> possible as the ISO is attached to the VM instance during the ins= tallation. > >>>>>>>=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 A= LPHA5. > >>>>>>=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 a= re > >>>>>> 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 sub= mit > >>>>>> 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 relea= se 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 w= ho > >>>>> 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-b= ox > >>>>> support on the premier commercial Xen platform we'll be shooting > >>>>> ourselves in the foot and all of this work will be for naught. Amaz= on > >>>>> 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-ALPHA5/amd64/ > >>>>=20 > >>=20 > >> This is way better. Having ready to import Xen images beats ISO instal= lation > >> any day. Will try on my cloudstack setup later today. > >=20 > > 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. > >=20 > > Oh well. > >=20 > > Thanks for all the help. > >=20 > > Regards. > > @shankerbalan >=20 > The CDROM issue should be resolved in FreeBSD/head. These fixes will be > include > in 10.0-BETA2 as well as the first 11-CURRENT snapshot that should pop up > in > the next day or two. The snapshots are announced on the > freebsd-snapshots > mailing list. >=20 Can you please backport to 9-STABLE? This issue is what is preventing me from upgrading my Xen infrastructure at work. Thanks so much! From owner-freebsd-xen@FreeBSD.ORG Sun Oct 13 16:31:00 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 6770DA07; Sun, 13 Oct 2013 16:31:00 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1E1832B0B; Sun, 13 Oct 2013 16:31:00 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id wm4so4125570obc.36 for ; Sun, 13 Oct 2013 09:30:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+hh/SrJQiW4dD4IeybvPdxCP942xTTt8I5Qh0mpyZq8=; b=EUn9pK19T1tjaVLeRHQbYGFI8Zm/wn6JDUPpAc/DgNSFRPXojEz5lgOC7/DRSCXYNX 4n/IN0gIB9aZpYvXoU7ufx8gbEyRhpnamt0iHdBulz/1mzjotSf8AMOtrYYXPv+p+MXy q6tEr48iqsJ4BjQ/27d6HOmDd8TkAAOHqbtjRgEw4+mKcjU6dudeZuugEZIBAk4dZqfG AX/3wSEw8pY5skMBYrE8VzZ/kGs+sib5mrdaaPpfrY3IZ/+i0cANwwMiFTIPHfm7FBVs NXk3gLtRjl6ysiJg3psgPKBuKxjbrXEZQlFobslfqWwCNf/YghbwSGQ4dGi4fjpZvuTA 7b1g== MIME-Version: 1.0 X-Received: by 10.60.62.172 with SMTP id z12mr5200876oer.4.1381681859280; Sun, 13 Oct 2013 09:30:59 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Sun, 13 Oct 2013 09:30:59 -0700 (PDT) In-Reply-To: <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> Date: Sun, 13 Oct 2013 12:30:59 -0400 Message-ID: Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem From: Outback Dingo To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-xen@freebsd.org 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, 13 Oct 2013 16:31:00 -0000 On Sun, Oct 13, 2013 at 10:58 AM, Mark Felder wrote: > > > On Sat, Oct 12, 2013, at 21:48, Justin T. Gibbs wrote: > > On Oct 10, 2013, at 3:09 AM, Shanker Balan > wrote: > > > > > > > > On 10-Oct-2013, at 1:37 PM, Shanker Balan > wrote: > > > > > >> On 09-Oct-2013, at 8:06 PM, Mark Felder wrote: > > >> > > >>> 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: > > >>>>>>> > > >>>>>>>> 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: > > >>>>>>>>> run_interrupt_driven_hooks - still waiting after 300 seconds > for > > >>>>>>>>> xenbusb_nop_confighook_cb > > >>>>>>>>> panic: run_interrupt_driven_config_hooks: waited too long > > >>>>>>>>> > > >>>>>>>> > > >>>>>>>> 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 thi= s > bug. > > >>>>>>>> > > >>>>>>>> Can someone working on the xen bits test and maybe find a > workaround? > > >>>>>>> > > >>>>>>> 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. > > >>>>>>> > > >>>>>>> A "please pretty please" request to @citrix R&D for the > hopefully last fix > > >>>>>>> to get FreeBSD 10 running on XenServer+CloudStack. > > >>>>>>> > > >>>>>>> The earlier HyperV related panic on XenServer has been fixed in > ALPHA5. > > >>>>>> > > >>>>>> Hello, > > >>>>>> > > >>>>>> I've taken a look into this and I'm afraid there's no easy way t= o > > >>>>>> workaround it from FreeBSD. When Xen is detected all IDE devices > are > > >>>>>> disconnected, and there's no fine grained way to only disable ID= E > disks > > >>>>>> and not cdrom devices. > > >>>>>> > > >>>>>> 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. > > >>>>>> > > >>>>> > > >>>>> Citrix is aware of this as I've contacted several people there an= d > 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 an= d > > >>>>> NetBSD have no issues. > > >>>> > > >>>> 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 hav= e > > >>>> PVHVM support, so it's quite clear it won't have this issue). > > >>>> > > >>>>> 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. > > >>>> > > >>>> The main problem here is that XenServer announces a PV block devic= e > 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 i= s > not > > >>>> with the device model (Qemu), but with the backend that should > handle > > >>>> this PV device. > > >>>> > > >>>> 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 a= t > 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). > > >>>> > > >>>>> 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 t= o > 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. > > >>>> > > >>>> 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). > > >>>> > > >>>> > ftp://ftp.nl.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/20131007/10.0-AL= PHA5/amd64/ > > >>>> > > >> > > >> 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 > > > > The CDROM issue should be resolved in FreeBSD/head. These fixes will b= e > > include > > in 10.0-BETA2 as well as the first 11-CURRENT snapshot that should pop = up > > in > > the next day or two. The snapshots are announced on the > > freebsd-snapshots > > mailing list. > > > > Can you please backport to 9-STABLE? This issue is what is preventing me > from upgrading my Xen infrastructure at work. > > Thanks so much! > confirmed to also work on Ubuntu/XEN/virt-manager on my laptop even :P with cd attached as before it would fail dmesg Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #0 c8b87aa(master): Sun Oct 13 10:53:25 EDT 2013 dingo@devel.xxxxxxx.com:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.3 detected. CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x306a9 Family =3D 0x6 Model =3D 0x3a Stepping =3D 9 Features=3D0x1783fbff Features2=3D0xffb82203 AMD Features=3D0x28100800 AMD Features2=3D0x1 Standard Extended Features=3D0x200 real memory =3D 2147483648 (2048 MB) avail memory =3D 2047053824 (1952 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-47 on motherboard random: initialized kbd1 at kbdmux0 xen_et0: on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: on acpi0 cpu1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 uhci0: port 0xc240-0xc25f irq 23 at device 1.2 on pci0 usbus0: controller did not stop usbus0 on uhci0 pci0: at device 1.3 (no driver attached) vgapci0: mem 0xf0000000-0xf1ffffff,0xf3020000-0xf3020fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: on xenpci0 pcm0: port 0xc100-0xc1ff irq 36 at device 5.0 on pci0 pcm0: atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! ppc0: cannot reserve I/O port range ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=3D0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 xenbusb_front0: on xenstore0 ugen0.1: at usbus0 uhub0: on usbus0 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:d2:55:c7 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 65536MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd0: features: flush, write_barrier xbd0: synchronize cache commands enabled. random: unblocking device. xbd1: 65536MB at device/vbd/832 on xenbusb_front0 xbd1: attaching as ada1 xbd1: features: flush, write_barrier xbd1: synchronize cache commands enabled. Netvsc initializing... SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered Trying to mount root from zfs:zroot/bootenv/default []... xn0: 2 link states coalesced xm info host : M14xR2 release : 3.11.0-12-generic version : #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 2494 hw_caps : bfebfbff:28100800:00000000:00007f00:77bae3bf:00000000:00000001:00000281 virt_caps : hvm total_memory : 8074 free_memory : 6 free_cpus : 0 xen_major : 4 xen_minor : 3 xen_extra : .0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xffff800000000000 xen_changeset : xen_commandline : placeholder cc_compiler : gcc (Ubuntu/Linaro 4.8.1-10ubuntu5) 4.8.1 cc_compile_by : stefan.bader cc_compile_domain : canonical.com cc_compile_date : Wed Oct 2 11:17:12 UTC 2013 xend_config_format : 4 > _______________________________________________ > 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" > From owner-freebsd-xen@FreeBSD.ORG Mon Oct 14 11:07:00 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 F159E584 for ; Mon, 14 Oct 2013 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE4912CA1 for ; Mon, 14 Oct 2013 11:06:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9EB6xQ8035426 for ; Mon, 14 Oct 2013 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9EB6xRP035424 for freebsd-xen@FreeBSD.org; Mon, 14 Oct 2013 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Oct 2013 11:06:59 GMT Message-Id: <201310141106.r9EB6xRP035424@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org 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: Mon, 14 Oct 2013 11:07:00 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/180788 xen [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot o kern/180403 xen [xen] Problems with GENERIC and XENHVM kernels with Xe o kern/180402 xen [xen] XEN kernel does not load in XenClient 4.5.5 o kern/179814 xen [xen] mountroot fails with error=19 under Xen on 9-STA o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 39 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 14 13:57:32 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 168CAD99 for ; Mon, 14 Oct 2013 13:57:32 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D94B02A02 for ; Mon, 14 Oct 2013 13:57:31 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A953B2235C for ; Mon, 14 Oct 2013 09:57:28 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute1.internal (MEProxy); Mon, 14 Oct 2013 09:57:28 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=25QTV8NS5smBFItkTSL3dHn+K8I=; b=PHEuH olcONbLyiPTVtfWEnDuJypy1me02teVRl3c6e6qlFZ04+zZhAoGux7QcvCGtEJpg 58K7hCGJkuSodjOL5s/rL8Fp0DHybYbBRJ1Mnf3/tM0fe+8+OmEWjtb3ccuiuC0+ vhBIQKtQ5ZsGOgRuELh2iCg0BN28gCkKesVNcc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 8B3DC11B4E1; Mon, 14 Oct 2013 09:57:28 -0400 (EDT) Message-Id: <1381759048.14147.33785945.2DAF9556@webmail.messagingengine.com> X-Sasl-Enc: tQP7tmxA1RM3biN5M8RshvimrOfuJGBw3qKZTdVh2uFW 1381759048 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem Date: Mon, 14 Oct 2013 08:57:28 -0500 In-Reply-To: <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> 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: Mon, 14 Oct 2013 13:57:32 -0000 Patching 9-STABLE with this applies cleanly, but I'm guessing the work done with the restructuring so it fits in GENERIC is not permitting it to build. /usr/src/sys/dev/xen/blkfront/blkfront.c: In function 'blkfront_probe': /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: implicit declaration of function 'xen_hvm_domain' /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: nested extern declaration of 'xen_hvm_domain' [-Wnested-externs] *** [blkfront.o] Error code 1 Stop in /usr/obj/usr/src/sys/XENHVM. *** [buildkernel] Error code 1 Stop in /usr/src. *** [buildkernel] Error code 1 Stop in /usr/src. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 14 14:29:00 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B7E0F997; Mon, 14 Oct 2013 14:29:00 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D50C22C56; Mon, 14 Oct 2013 14:28:59 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.93,492,1378857600"; d="scan'208";a="63363279" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 14 Oct 2013 14:28:57 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Mon, 14 Oct 2013 10:28:56 -0400 Message-ID: <525BFFAD.4010208@citrix.com> Date: Mon, 14 Oct 2013 16:29:01 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Mark Felder Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> <1381759048.14147.33785945.2DAF9556@webmail.messagingengine.com> In-Reply-To: <1381759048.14147.33785945.2DAF9556@webmail.messagingengine.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-DLP: MIA1 Cc: freebsd-xen@freebsd.org 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: Mon, 14 Oct 2013 14:29:00 -0000 On 14/10/13 15:57, Mark Felder wrote: > Patching 9-STABLE with this applies cleanly, but I'm guessing the work > done with the restructuring so it fits in GENERIC is not permitting it > to build. > > > /usr/src/sys/dev/xen/blkfront/blkfront.c: In function 'blkfront_probe': > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: implicit > declaration of function 'xen_hvm_domain' > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: nested extern > declaration of 'xen_hvm_domain' [-Wnested-externs] > *** [blkfront.o] Error code 1 > > Stop in /usr/obj/usr/src/sys/XENHVM. > *** [buildkernel] Error code 1 > > Stop in /usr/src. > *** [buildkernel] Error code 1 > > Stop in /usr/src. Yes, the xen_hvm_domain function is not available in 9-STABLE, you should be able to replace the 'if' gate with a '#ifdef XENHVM .. #endif' (not pretty, but should do it's job). Roger. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 14 15:17:22 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7772F345; Mon, 14 Oct 2013 15:17:22 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 44AAD2F55; Mon, 14 Oct 2013 15:17:21 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id DDD3E21A12; Mon, 14 Oct 2013 11:17:15 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Mon, 14 Oct 2013 11:17:16 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=w5PvgE9Tl64QAEO4AtBHkxzt300=; b=Gu4 8soTFU6/8LN/brc4zwwAPcMJO1lNECpo0/wELZVRWfrWyMCfJB8TKyUT+1QjC0YD oVhVPBA35DdK9fII+rNTMmWynjJvNE81NiJpuEOJHkutIvLYbK343DTdYr7GWanm 8mQhnePsZ/dfXDbK8FzP6ij6/k7BtM16O3lg7QoA= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 6F7586E0AD6; Mon, 14 Oct 2013 11:17:15 -0400 (EDT) Message-Id: <1381763835.23774.33816289.4C29471F@webmail.messagingengine.com> X-Sasl-Enc: 7XHht0guQ+jdZkp0hUTNsal0t578nAKk7I8iHQD3rNxi 1381763835 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: <525BFFAD.4010208@citrix.com> 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> <1381759048.14147.33785945.2DAF9556@webmail.messagingengine.com> <525BFFAD.4010208@citrix.com> Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem Date: Mon, 14 Oct 2013 10:17:15 -0500 Cc: gibbs@freebsd.org 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: Mon, 14 Oct 2013 15:17:22 -0000 On Mon, Oct 14, 2013, at 9:29, Roger Pau Monn=E9 wrote: > On 14/10/13 15:57, Mark Felder wrote: > > Patching 9-STABLE with this applies cleanly, but I'm guessing the work > > done with the restructuring so it fits in GENERIC is not permitting it > > to build. > >=20 > >=20 > > /usr/src/sys/dev/xen/blkfront/blkfront.c: In function 'blkfront_probe': > > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: implicit > > declaration of function 'xen_hvm_domain' > > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: nested extern > > declaration of 'xen_hvm_domain' [-Wnested-externs] > > *** [blkfront.o] Error code 1 > >=20 > > Stop in /usr/obj/usr/src/sys/XENHVM. > > *** [buildkernel] Error code 1 > >=20 > > Stop in /usr/src. > > *** [buildkernel] Error code 1 > >=20 > > Stop in /usr/src. >=20 > Yes, the xen_hvm_domain function is not available in 9-STABLE, you > should be able to replace the 'if' gate with a '#ifdef XENHVM .. #endif' > (not pretty, but should do it's job). >=20 I have just tested that patched on FreeBSD 9.1-p7 and it works perfectly. I am able to boot the OS with no issues and mounting CDROMs works fine as well. One thing to note is that it does change the disk from /dev/adX to /dev/adaX which is something that was happening between FreeBSD 9 and FreeBSD 10 anyway. Anyone who applies this patch should update their fstab before rebooting. https://feld.me/freebsd/freebsd9-xen-cdrom-fix.patch Thanks again Roger and Justin -- you've just made a huge impact in FreeBSD usability on XenServer. From owner-freebsd-xen@FreeBSD.ORG Mon Oct 14 15:28:52 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 EF8FF510; Mon, 14 Oct 2013 15:28:52 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9992C2FF5; Mon, 14 Oct 2013 15:28:52 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id i7so4538189oag.26 for ; Mon, 14 Oct 2013 08:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rsmHMduDaTZsW19pg/SdJLM7OvsHAM8+VErVO8RWMmA=; b=XWTKJu0/rqrqzARh9OtZSwAcx67Qm+GC2D8nWOr5BgpdWM69msVgmU03+BevqiI623 WNR/Lppt588MZTAtoRZvB9hXIHkgH3aI4y2gUWtoP2NpX93gc2IBZYBetSPIhPnJq2MI a39RZD4uUQ3U6IJKKHVIn2U2PEi8VRB6bOrQS5T2gGBH2xNUmpn+0nlrnfBQpkzxxIcD YyqT0J1bXyCnWb4SsIV6TQ2XnuILQkXRztb8ZJW0IBjkpU/Zk58dlEY8iZkzQqvoyHJ2 GdMCI+KdhiIsmlTjNT84J/ueVtSqGdlD1NhbhJTSszTQPq18ygpic2HkzsZLc+OFVWv/ HLTg== MIME-Version: 1.0 X-Received: by 10.182.227.136 with SMTP id sa8mr2372786obc.39.1381764531731; Mon, 14 Oct 2013 08:28:51 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 14 Oct 2013 08:28:51 -0700 (PDT) In-Reply-To: <1381763835.23774.33816289.4C29471F@webmail.messagingengine.com> 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> <7B7BC687-3A64-4B3D-9F90-B73FC6938225@shankerbalan.net> <1381676322.11187.33436965.1BBB5473@webmail.messagingengine.com> <1381759048.14147.33785945.2DAF9556@webmail.messagingengine.com> <525BFFAD.4010208@citrix.com> <1381763835.23774.33816289.4C29471F@webmail.messagingengine.com> Date: Mon, 14 Oct 2013 11:28:51 -0400 Message-ID: Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem From: Outback Dingo To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-xen@freebsd.org, gibbs@freebsd.org 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: Mon, 14 Oct 2013 15:28:53 -0000 On Mon, Oct 14, 2013 at 11:17 AM, Mark Felder wrote: > On Mon, Oct 14, 2013, at 9:29, Roger Pau Monn=E9 wrote: > > On 14/10/13 15:57, Mark Felder wrote: > > > Patching 9-STABLE with this applies cleanly, but I'm guessing the wor= k > > > done with the restructuring so it fits in GENERIC is not permitting i= t > > > to build. > > > > > > > > > /usr/src/sys/dev/xen/blkfront/blkfront.c: In function 'blkfront_probe= ': > > > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: implicit > > > declaration of function 'xen_hvm_domain' > > > /usr/src/sys/dev/xen/blkfront/blkfront.c:405: warning: nested extern > > > declaration of 'xen_hvm_domain' [-Wnested-externs] > > > *** [blkfront.o] Error code 1 > > > > > > Stop in /usr/obj/usr/src/sys/XENHVM. > > > *** [buildkernel] Error code 1 > > > > > > Stop in /usr/src. > > > *** [buildkernel] Error code 1 > > > > > > Stop in /usr/src. > > > > Yes, the xen_hvm_domain function is not available in 9-STABLE, you > > should be able to replace the 'if' gate with a '#ifdef XENHVM .. #endif= ' > > (not pretty, but should do it's job). > > > > I have just tested that patched on FreeBSD 9.1-p7 and it works > perfectly. I am able to boot the OS with no issues and mounting CDROMs > works fine as well. One thing to note is that it does change the disk > from /dev/adX to /dev/adaX which is something that was happening between > FreeBSD 9 and FreeBSD 10 anyway. Anyone who applies this patch should > update their fstab before rebooting. > > https://feld.me/freebsd/freebsd9-xen-cdrom-fix.patch > > Thanks again Roger and Justin -- you've just made a huge impact in > FreeBSD usability on XenServer. > Congrats, finally we have some parity with XEN and Cloud for FreeBSD.... > _______________________________________________ > 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" > From owner-freebsd-xen@FreeBSD.ORG Thu Oct 17 08:30:59 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 8B98E2FC for ; Thu, 17 Oct 2013 08:30:59 +0000 (UTC) (envelope-from Pekka.Panula@sofor.fi) Received: from mail1.netservant.fi (mail1.netservant.fi [213.250.93.2]) by mx1.freebsd.org (Postfix) with ESMTP id 18E292CB1 for ; Thu, 17 Oct 2013 08:30:58 +0000 (UTC) Received: by mail1.netservant.fi (Postfix, from userid 502) id 9DE6762D12E; Thu, 17 Oct 2013 11:11:37 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.netservant.fi X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.1 Received: from mail1.netservant.fi (mail1.sofor.fi [127.0.0.1]) by mail1.netservant.fi (Postfix) with ESMTP id A567F62D131 for ; Thu, 17 Oct 2013 11:11:36 +0300 (EEST) Received: from sofextr4.sofor.fi (sofextr4.sofor.fi [213.250.93.71]) by mail1.netservant.fi (Postfix) with ESMTP id 991E362D12E for ; Thu, 17 Oct 2013 11:11:36 +0300 (EEST) To: freebsd-xen@freebsd.org MIME-Version: 1.0 Subject: FreeBSD 10.0-Beta1 OVA appliance for XenServer 6.2 X-KeepSent: 1FA033E4:7B4BC6AD-C2257C07:002BAECD; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0 March 08, 2013 Message-ID: From: Pekka.Panula@sofor.fi Date: Thu, 17 Oct 2013 11:11:23 +0300 X-Virus-Scanned: ClamAV using ClamSMTP Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 17 Oct 2013 08:30:59 -0000 Hi As you all know, you cant install FreeBSD 10.0-Beta1 from ISO CD under XenServer 6.2, because cd-rom problem it has. Hope its somehow fixed in future. Anyway, i managed to install it thru PXE-TFTP method. PXE install method has some little bugs, like its trying to re-mount root as read-write (cant do that) so you need to modify /etc/fstab and remove line from there. Also not sure about why name servers did not work as my DHCP is giving out correct DNS servers, so it was also needed to modify /etc/resolv.conf and put out nameservers there, then you can install it correctly. My boot source was FreeBSD-10.0-BETA1-amd64-bootonly.iso, i unpacked it to TFTP server and used that as root. Could give my DHCP config if anyone is also interested to bootstrap from PXE-TFTP method. Here is a download URL for OVA file i made for FreeBSD 10.0-Beta1, AMD64: http://download.sofor.fi/FreeBSD10.0-BETA1.ova.gz, size about 373MB packed. its installed as ZFS on root. root pw: password, it also has pkgng working pointed to http://mirror.exonetric.net/pub/pkgng/freebsd%3A10%3Ax86%3A64/ so i managed to install Xen Tools easy way. One notice regarding Xen Tools, when you do shutdown option from XenCenter its not actually seems to be shutdowning, it says its halted and it waiting key press to reboot. I am hoping that is modified in future and shutdown actually shutdowns it as now it leaves its running state under XenServer. Not sure if there is a bug report open for that. Regards, Pekka Panula From owner-freebsd-xen@FreeBSD.ORG Thu Oct 17 15:20:19 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 E837057F for ; Thu, 17 Oct 2013 15:20:19 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC84E299C for ; Thu, 17 Oct 2013 15:20:19 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B846420F49; Thu, 17 Oct 2013 11:20:12 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Thu, 17 Oct 2013 11:20:12 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=D6YOUsSLBE5R0kjiugMS0i16bLk=; b=ZtpU+ 5SLb6USCLVJQKsfDTr5UlyMZp+0p/2I0LEj4D3VA8Wpg6IaQPghy6hrJ8ND1rARr Hgn46HyI/WuZpDxVV64w8J/zbbsicYzPJclLUAHY7K4hILANhdieAOQjTkr2c4hZ PZh1vub76m6F19L7i3ffIX6snUVUY3S9xJ7siU= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 8EA225818FD; Thu, 17 Oct 2013 11:20:12 -0400 (EDT) Message-Id: <1382023212.5295.35193809.65F0A86A@webmail.messagingengine.com> X-Sasl-Enc: 6dv1MM+WJMK5SI1O0t7RqLXiyX8aqYKLkYhCUt7cQbLu 1382023212 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 Subject: Re: FreeBSD 10.0-Beta1 OVA appliance for XenServer 6.2 Date: Thu, 17 Oct 2013 10:20:12 -0500 In-Reply-To: References: 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, 17 Oct 2013 15:20:20 -0000 On Thu, Oct 17, 2013, at 3:11, Pekka.Panula@sofor.fi wrote: > Hi > > As you all know, you cant install FreeBSD 10.0-Beta1 from ISO CD under > XenServer 6.2, because cd-rom problem it has. Hope its somehow fixed in > future. > Hi Pekka! This has been fixed in 10-STABLE and will be part of the next BETA release :-) There is also a patch for FreeBSD 9 that they will hopefully backport. Note, this patch is slightly different than the one required for 10-STABLE. Big thanks to gibbs and Roger for their work on Xen. https://feld.me/freebsd/freebsd9-xen-cdrom-fix.patch > One notice regarding Xen Tools, when you do shutdown option from > XenCenter > its not actually seems to be shutdowning, it says its halted and it > waiting key press to reboot. > I am hoping that is modified in future and shutdown actually shutdowns it > as now it leaves its running state under XenServer. Not sure if there is > a > bug report open for that. > I do have a bug report for that -- kern/171118. I had a conversation with someone not too long ago that I'm looking for in my email. It was suggested that XenServer sends the wrong command.