From owner-freebsd-xen@FreeBSD.ORG Mon Oct 19 11:07:05 2009 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1A2D1065695 for ; Mon, 19 Oct 2009 11:07:05 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D09188FC25 for ; Mon, 19 Oct 2009 11:07:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9JB75Tv063626 for ; Mon, 19 Oct 2009 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9JB75qc063624 for freebsd-xen@FreeBSD.org; Mon, 19 Oct 2009 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Oct 2009 11:07:05 GMT Message-Id: <200910191107.n9JB75qc063624@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 Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Oct 2009 11:07:06 -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/136251 xen [xen] [patch] xn0 doesn't DHCP o kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. o kern/135179 xen [xen] Xen domU does not properly reboot o kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all o kern/135008 xen [xen] FreeBSD-current/Xen timecounter jumps o kern/134926 xen [xen] [panic] FreeBSD-current Xen DomU networking pani 7 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 20 22:12:35 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9ACD10656A5; Tue, 20 Oct 2009 22:12:35 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (113901-app1.sourcehosting.net [72.32.213.11]) by mx1.freebsd.org (Postfix) with ESMTP id B18148FC1B; Tue, 20 Oct 2009 22:12:35 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N0MwP-000Lcs-9w; Tue, 20 Oct 2009 18:12:34 -0400 Received: from [127.0.0.1] (fireball.entropy.prv [192.168.1.12]) by cube.entropy.prv (Postfix) with ESMTP id CF82D363E292; Tue, 20 Oct 2009 18:12:29 -0400 (EDT) Message-ID: <4ADE35CC.3070108@FreeBSD.org> Date: Tue, 20 Oct 2009 18:12:28 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Martin Cracauer References: <77abe410908211256g44dd20d8o9b50c20357e63a6b@mail.gmail.com> <4A94CD0D.8070902@prgmr.com> <4ACFEC6E.2030109@FreeBSD.org> <20091010150224.GA71643@cons.org> In-Reply-To: <20091010150224.GA71643@cons.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=1C940290 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) Cc: freebsd-xen@freebsd.org Subject: Re: finishing up the xen port - would funding help? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org 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, 20 Oct 2009 22:12:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Cracauer wrote: > Greg Larkin wrote on Fri, Oct 09, 2009 at 10:07:42PM -0400: >> I also figured that it might take even more time to >> then port to the version of Xen used by Amazon. > > What version is that and why do they assume they are still using it > when the port is finished? > > Martin Hi Martin, As far as I know, Amazon is using Xen 3.0.3 (according to http://wiki.freebsd.org/FreeBSD/Xen), but it's possible that it has been upgraded. I'll see if I can get an update from my contact at Amazon. Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK3jXM0sRouByUApARAuNCAJ9zgYdU5E1mqaDLOQnli7hdcqpbmQCfdw3v QpmtaNK4nHjLWK/D1VzuAC8= =hNyI -----END PGP SIGNATURE----- From owner-freebsd-xen@FreeBSD.ORG Tue Oct 20 22:13:19 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CDCF1065692; Tue, 20 Oct 2009 22:13:19 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (113901-app1.sourcehosting.net [72.32.213.11]) by mx1.freebsd.org (Postfix) with ESMTP id EA6428FC14; Tue, 20 Oct 2009 22:13:18 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N0Mx6-000Ldz-NK; Tue, 20 Oct 2009 18:13:17 -0400 Received: from [127.0.0.1] (fireball.entropy.prv [192.168.1.12]) by cube.entropy.prv (Postfix) with ESMTP id 408B7363E2D5; Tue, 20 Oct 2009 18:13:13 -0400 (EDT) Message-ID: <4ADE35F8.5070901@FreeBSD.org> Date: Tue, 20 Oct 2009 18:13:12 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Adrian Chadd References: <77abe410908211256g44dd20d8o9b50c20357e63a6b@mail.gmail.com> <4A94CD0D.8070902@prgmr.com> <4ACFEC6E.2030109@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=1C940290 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) Cc: freebsd-xen@freebsd.org Subject: Re: finishing up the xen port - would funding help? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org 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, 20 Oct 2009 22:13:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian Chadd wrote: > Please contact the FreeBSD foundation and let them know that Amazon > contacted you. The best thing to do IMHO is get Amazon and the > Foundation discussing Xen related things before involving developers. > > Thanks, > > > > Adrian > Hi Adrian, Ok, that sounds like a great idea - will do. Cheers, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK3jX40sRouByUApARAk83AJ4xjMBN/Z6MMQ34RPBzR4Rb/4PNIQCgv9y4 W7M8aLAPibjgtW4giZJ3kyk= =I2mi -----END PGP SIGNATURE----- From owner-freebsd-xen@FreeBSD.ORG Sat Oct 24 21:03:23 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37536106568B for ; Sat, 24 Oct 2009 21:03:23 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id E9F678FC1B for ; Sat, 24 Oct 2009 21:03:22 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id EFC60ED0997 for ; Sat, 24 Oct 2009 21:43:14 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; s=selector1; bh=+CspBpL+JaFPqjPy7Q9FiwvqiEM=; b= SSMBelrWMpuYr3M7aW0S1Rb/vTm68EQ9zpsYSFU3BJYRYiwGxpi+QhCOi8/mGgxH s/wySej0WlKJxY1VeyfxQ5KY7WI3ULqcpWr/ouGrVkSM0bG0jEjHUAY5Yy+Kix0E 3Sx+R8EeDuJBzLRTOMqAeROJ28KZZj1E1HA0E+0qWVQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; q=dns; s=selector1; b=bB4+hDYhMrDPw8KC3dPC0RhT 2F5nHOFzQPxb3FPasCogfj3rKVFp5h6kKo7y6BVEXBvSUAKh5/kGN7/+UmxqeaCt lOM+swqLXmWbpJP+C/ndESrYxNMJyORCdhcdOiVQU8CMeE8Jkr4Lns+vazJMpSU7 4b2qUugr1XocVZiSeYU= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id BF486ED0994 for ; Sat, 24 Oct 2009 21:43:14 +0100 (BST) From: Carsten Heesch Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Sat, 24 Oct 2009 21:43:14 +0100 Message-Id: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) Subject: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 24 Oct 2009 21:03:23 -0000 Hi guys, I don't know really when the bug was introduced, but maybe I can help narrowing it down. I have similar problems as others reported: Running FreeBSD 8.0-RC1 as a guest in a Xen 3.3.1 environment fails with either "kernel trap 12" in an endless loop (using amd64) or "kernel trap 9" (using i386). For 8.0-RC1 it doesn't make a difference if it's a clean install, in which case I wouldn't even be able to start the installer, or a "freebsd-update upgrade -r 8.0-RC1" from 7.2-RELEASE, in which case it wouldn't reboot with the newly compiled kernel. Funnily one of the earlier betas (not sure which one it exactly was, and can't reproduce any more, as they are not available on any mirrors), and 8.0-SNAPSHOT-200906 (tested today) both work without any problems. With the snapshot, I was also able to build a XENHVM kernel, which boots fine, and offers the XENHVM network and block devices. The environment I'm testing on is: - Intel i7 920, 12 GB RAM - Dom0 is running on CentOS 5.2 and Xen 3.3.1 (Citrix XenServer 5.5) Is there any way to extract relevant information, which would help you to fix it? I'd really like to see FreeBSD 8.0-RELEASE working on Xen! So if there is anything you need to know, please tell me what it is, and how I can gather it. Cheers Carsten From owner-freebsd-xen@FreeBSD.ORG Sat Oct 24 23:50:03 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2423106566B for ; Sat, 24 Oct 2009 23:50:03 +0000 (UTC) (envelope-from carsten@heesch.me.uk) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 593EE8FC13 for ; Sat, 24 Oct 2009 23:50:02 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 75B72ED0997; Sun, 25 Oct 2009 00:31:51 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=heesch.me.uk; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=rxh2hrzUQi/6KxDMSWq+ZR1VREw=; b=CJUpPbwA7zHEBiFU5m Ol+Uy6YVTOfSgQ4k+EQkqT6UbjGxhEw6E00sN1wzpSOx9t4Occe1HAcd2DYwwMgx 1opDkB7pe6CzMs+6HBW8nTD1NArV+wxzhU/GFhdzwzgPhTSnTiywVNzkmlsPyxFF 2QqssXWpLoOnOdSdwsgn2S+kY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=heesch.me.uk; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=bYPPT41XmKqbiHTXJhJ1P/Dav3eG/i/+vSOQBfIaXShPM6Qugj9 xUbTD+DXeXUyPWsjnwEyHiwiJFnXmVhBr4NWlNCCAc4H7o3rxzeWIKhqUTomaP9H 5MtMyqfby0uxDPLPCllG5E1TqE920RH2OYMSqbfsusBHXB6j9UN1rOYI= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 32D4FED0994; Sun, 25 Oct 2009 00:31:51 +0100 (BST) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Carsten Heesch In-Reply-To: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> Date: Sun, 25 Oct 2009 00:31:50 +0100 Content-Transfer-Encoding: 7bit Message-Id: <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> To: Carsten Heesch X-Mailer: Apple Mail (2.1076) Cc: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 24 Oct 2009 23:50:03 -0000 I realised that it's still possible to use 8.0-BETA* as a target for freebsd-update. So I investigated a bit further. For whatever it's worth: The problems described earlier started with BETA-4. BETA-3 is fine with both GENERIC and XENHVM kernel, except that I see this on the console and in dmesg every now and then (with both kernels): lock order reversal: 1st 0xffffff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/ vfs_bio.c:2559 2nd 0xffffff00015a7c00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ ufs_dirhash.c:285 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_xlock() at _sx_xlock+0x55 ufsdirhash_acquire() at ufsdirhash_acquire+0x33 ufsdirhash_add() at ufsdirhash_add+0x19 ufs_direnter() at ufs_direnter+0x88b ufs_makeinode() at ufs_makeinode+0x31c VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x423 kern_openat() at kern_openat+0x179 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = 0x7fffffffe608, rbp = 0x1a4 --- I though this might be XENHVM kernel related, but it happens with GENERIC kernel as well. Not sure if this is related to XEN at all. Cheers Carsten