From owner-freebsd-xen@FreeBSD.ORG Sun Oct 14 13:52:43 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 50633566 for ; Sun, 14 Oct 2012 13:52:43 +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 058678FC0C for ; Sun, 14 Oct 2012 13:52:42 +0000 (UTC) Received: from [192.168.12.224] (unknown [212.81.198.13]) by proxypop03.sare.net (Postfix) with ESMTPSA id 46E849DC9C3; Sun, 14 Oct 2012 15:51:38 +0200 (CEST) Subject: Re: xenbusb_nop_confighook_cb timeout Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=windows-1252 From: Egoitz Aurrekoetxea Aurre In-Reply-To: <9512D202-F84C-435A-8E45-5E6B976733C4@ramattack.net> Date: Sun, 14 Oct 2012 15:52:32 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <56220767-2785-4B15-97FE-8480528939E2@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> To: Mark Felder X-Mailer: Apple Mail (2.1499) Cc: "freebsd-xen@freebsd.org" , =?windows-1252?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 13:52:43 -0000 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 = 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 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" 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" From owner-freebsd-xen@FreeBSD.ORG Mon Oct 15 11:06:15 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 643EF521 for ; Mon, 15 Oct 2012 11:06:15 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 31CE38FC2D for ; Mon, 15 Oct 2012 11:06:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9FB6FJt011678 for ; Mon, 15 Oct 2012 11:06:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9FB6Fd5011677 for freebsd-xen@FreeBSD.org; Mon, 15 Oct 2012 11:06:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Oct 2012 11:06:15 GMT Message-Id: <201210151106.q9FB6Fd5011677@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, 15 Oct 2012 11:06:15 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). From owner-freebsd-xen@FreeBSD.ORG Mon Oct 15 18:31:16 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 51CBA643 for ; Mon, 15 Oct 2012 18:31:16 +0000 (UTC) (envelope-from arvind.viswanathan@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 324298FC0C for ; Mon, 15 Oct 2012 18:31:15 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TNpRb-0007Ws-CY for freebsd-xen@freebsd.org; Mon, 15 Oct 2012 11:31:15 -0700 Date: Mon, 15 Oct 2012 11:31:15 -0700 (PDT) From: bv_arvind To: freebsd-xen@freebsd.org Message-ID: <1350325875377-5752251.post@n5.nabble.com> Subject: Freebsd 7 with xen ports not working with secondary harddisk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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, 15 Oct 2012 18:31:16 -0000 Hi, I ported xen changes to FreeBSD 7 and it came up fine and i am able to forward using the interfaces. When I tried to create a new virtual harddisk and format it I get a core dump. The core dump file does not seem to point to anywhere. Here are the relevant dmesg: xbd0: 40961MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xctrl0: on xenstore0 nbusb_front0 xbd1: attaching as ad1 o/p of /dev: AN# ls | grep ad ad0 ad0s1 ad0s1a ad0s1b ad0s1c ad0s1d ad0s1e ad0s1f ad0s1g ad1 The device got attached correctly as well. However after zeroing the boot sector, trying to create a bsdlabel results in error, AN# dd if=/dev/zero of=/dev/ad1 bs=64k count=1 1+0 records in 1+0 records out 65536 bytes transferred in 0.000834 secs (78581449 bytes/sec) AN# bsdlabel -w ad1 Segmentation fault (core dumped) Thanks Arvind -- View this message in context: http://freebsd.1045724.n5.nabble.com/Freebsd-7-with-xen-ports-not-working-with-secondary-harddisk-tp5752251.html Sent from the freebsd-xen mailing list archive at Nabble.com. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 16 15:13:28 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 824309AC for ; Tue, 16 Oct 2012 15:13:28 +0000 (UTC) (envelope-from "") Received: from mail5.prolinkweb.com.br (mail5.prolinkweb.com.br [66.240.192.143]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9238FC0C for ; Tue, 16 Oct 2012 15:13:28 +0000 (UTC) Received: from (localhost [117.5.179.222]) by mail5.prolinkweb.com.br (mail.prolinkweb.com.br) with SMTP id AZB26916 for ; Tue, 16 Oct 2012 12:11:16 -0300 Date: Tue, 16 Oct 2012 12:11:16 -0300 From: Yann Nasi de Viaud To: Subject: Re: DELIVERY REPORTS ABOUT YOUR E-MAIL Message-Id: <1095786856@mail5.prolinkweb.com.br> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit 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: Tue, 16 Oct 2012 15:13:28 -0000 From owner-freebsd-xen@FreeBSD.ORG Thu Oct 18 13:54:46 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 64C4FDA7 for ; Thu, 18 Oct 2012 13:54:46 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop04b.sare.net (proxypop04b.sare.net [194.30.0.79]) by mx1.freebsd.org (Postfix) with ESMTP id 1D69D8FC19 for ; Thu, 18 Oct 2012 13:54:45 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id AB21E9DC688 for ; Thu, 18 Oct 2012 15:46:38 +0200 (CEST) From: Borja Marcos Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Fun with FreeBSD 9.1 and Xen Cloud 1.6 Date: Thu, 18 Oct 2012 15:47:23 +0200 Message-Id: <6FF8A9C7-CC9E-40B6-BEBC-CB2ABE91967C@sarenet.es> To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) 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, 18 Oct 2012 13:54:46 -0000 Hello, We've been doing some tests with FreeBSD and Xen Cloud 1.6 beta, with = some surprising results. Our test bed, for now, is a single Xen Cloud host, and the storage = backend, for now connected through one Gigabit Ethernet interface. We = are using NFS, tweaking a little the Xen Cloud scripts so that it uses = NFSv4. It works. The storage server has a ZFS pool of 7 SSD disks, configured as a raidz2 = group. The disks are connected to the SAS backplane of a Dell R410 = server, wired to a Dell H200 flashed so that it won't insist on = creating RAID volumes: it works as a HBA. The OS is FreeBSD 9.1-RC2. We have found an enormous difference in performance for the FreeBSD = virtual machines. The effect of tweaking the "sync" property for the = dataset in the storage server is dramatic for the XENHVM kernel, less = marked for the GENERIC kernel.=20 The benchmark we have used is Bonnie++, and the write performance (what = it calls "intelligent writing") shows this dramatic difference: GENERIC XENHVM = =20 zfs sync=3Dstandard ~ 30 MB/s ~6 MB/s zfs sync=3Ddisabled ~55 MB/s ~80 MB/s The read performance is irrelevant, it saturates the 1 Gbps interface in = both cases, as expected. The surprising results is: we get a terrible performance with the XENHVM = kernel when we leave the default setting of "sync=3Dstandard" for the = ZFS dataset. This setting, even with a performance hit, is preferred to = guaranteee the integrity of the virtual disk images in case of a crash = or outage. And when this happens, of course it ruins the performance for = all the other virtual machines, in case we have several running. Seems = it's insisting on flushing the ZIL constantly. Any ideas?=20 The GENERIC kernel is detecting the disk like thsi: atapci0: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc220-0xc22f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 device ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes) ada0: 20480MB (41943040 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 SMP: AP CPU #1 Launched! and the XENHVM kernel detects this: xbd0: 20480MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 GEOM: ad0s1: geometry does not match label (16h,63s !=3D 255h,63s). (I tried patching /usr/src/sys/dev/xen/blkfront/blkfront.c to force it = to attach the new ATA driver instead of the old one, but the result is = still the same.=20 Borja.