From owner-freebsd-xen@FreeBSD.ORG Mon Feb 7 11:07:14 2011 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 51FCB10656D7 for ; Mon, 7 Feb 2011 11:07:14 +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 26F9C8FC16 for ; Mon, 7 Feb 2011 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p17B7E1v027936 for ; Mon, 7 Feb 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p17B7D7h027934 for freebsd-xen@FreeBSD.org; Mon, 7 Feb 2011 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Feb 2011 11:07:13 GMT Message-Id: <201102071107.p17B7D7h027934@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, 07 Feb 2011 11:07:14 -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/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/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar 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 o 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 21 problems total. From owner-freebsd-xen@FreeBSD.ORG Sat Feb 12 08:23:43 2011 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 E96CB1065672; Sat, 12 Feb 2011 08:23:43 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id A9F198FC1A; Sat, 12 Feb 2011 08:23:43 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p1C8NeGE075177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 12 Feb 2011 08:23:40 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p1C8NeGE075177 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1297499021; x=1298103821; bh=z1u+9xOXNv+ysUXf8PIybEjj0l2vx1GjxCe2o0TfACI=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=gx0cQCerY7dmDUUEQYwEQFDhz9N49B/4NYeLOIf/nF0TKI5GevFjTx2qsRsVF2hZw 1SjiFJYe2krIg+ksPHp1jNr+Rs3eDdujW/vB4VJr+OKmMQcTR340NEBi9w7o9Pj/wW bzDdzi5RYY1REn4abfP46zc7KppfJSpTEYp+jR0c= Date: Sat, 12 Feb 2011 08:23:40 +0000 (UTC) From: Janne Snabb To: "Justin T. Gibbs" In-Reply-To: <4D474C3F.1010407@FreeBSD.org> Message-ID: References: <1295969742.3187.48.camel@pow> <4D474C3F.1010407@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Sat, 12 Feb 2011 08:23:41 +0000 (UTC) Cc: freebsd-xen@FreeBSD.org, luke@hybrid-logic.co.uk Subject: Re: I have a problem with iSCSI on AMD64 Xen HVM 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, 12 Feb 2011 08:23:44 -0000 Justin, Thanks for your comments regarding the state of Xen on FreeBSD. On Mon, 31 Jan 2011, Justin T. Gibbs wrote: > I sympathize with your desire for more code comments to make it easier to > ramp up on Xen. Unfortunately, there is little documentation about Xen > other than the "Linux reference implementation", and it is usually quite > terse in the comments department. This lack of documentation about Xen is the biggest turn-off for me regarding Xen. I started learning about Xen recently, and was very surprised and disappointed to notice that there is no real documentation nor specs about xenbus, xenstore contents, interfaces to basic devices (like net & blk), etc. I was expecting there to be more formal documentation available especially given that there are many big corporate entities involved in Xen. Maybe they have some internal specs which they are not releasing... Lack of interface specifications makes it impossible for example to write drivers which are more or less guaranteed to work with future versions of Xen as well as the current version. Now the process of writing anything would be to study/"reverse-engineer" Linux source code to understand what it does, and then re-implement the same functionality with new code. Not the best way of doing things. Just my thoughts... -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Sat Feb 12 09:00:42 2011 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 A45C6106566C; Sat, 12 Feb 2011 09:00:42 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 30B1E8FC14; Sat, 12 Feb 2011 09:00:42 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p1C90f7r034493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 12 Feb 2011 09:00:41 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p1C90f7r034493 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1297501241; x=1298106041; bh=CW4d8lDKOzgum/fYMgC6KkvfhGVbPTrUMfsGrYjxfsc=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=AADcToeZSkAa9S8BzWH6xLGil9I/LhvTU4r1wT83zf+TyeMtztRk7XNWUnt5BYavq MPyakbMhyOCyW00rtN5W73nk1O9Q4treog7UBtlB8tQu9W7Mf/r6Jcxd0FoscXuJtZ 9/TF40JAV2G4nDLbvIntLZG6GwMQ7o2B5EE9uIbU= Date: Sat, 12 Feb 2011 09:00:41 +0000 (UTC) From: Janne Snabb To: "Justin T. Gibbs" In-Reply-To: <4D47514C.7090706@FreeBSD.org> Message-ID: References: <4D47514C.7090706@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Sat, 12 Feb 2011 09:00:41 +0000 (UTC) Cc: freebsd-xen@FreeBSD.org Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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, 12 Feb 2011 09:00:42 -0000 On Mon, 31 Jan 2011, Justin T. Gibbs wrote: [..] > but Xend populates the MAC node in the frontend's tree > unless the "ioemu" tag is in the VIF configuration line for that interface. > Why this is the case, I have no idea - again the behavior is not documented. You are indeed correct. When I change: vif = [ 'type=ioemu, bridge=br0' ] ...to: vif = [ 'bridge=br0' ] ...in the configuration file for my FreeBSD XENHVM domU, the mac node magically appears on the front-end side: # xenstore-read device/vif/0/mac 00:16:3e:69:3e:99 ...and thus my patch becomes irrelevant. This is confusing. Especially because all the example configurations shipped with Xen have 'type=ioemu' in their vif definitions. I'll update the PR to include this workaround. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Sat Feb 12 09:20:10 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48E6F1065672 for ; Sat, 12 Feb 2011 09:20:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 37EC48FC35 for ; Sat, 12 Feb 2011 09:20:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1C9KAXf073400 for ; Sat, 12 Feb 2011 09:20:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1C9KAEe073399; Sat, 12 Feb 2011 09:20:10 GMT (envelope-from gnats) Date: Sat, 12 Feb 2011 09:20:10 GMT Message-Id: <201102120920.p1C9KAEe073399@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Janne Snabb Cc: Subject: Re: kern/154302: xn0: Error 2 parsing device/vif/0/mac [WORKAROUND] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Janne Snabb 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, 12 Feb 2011 09:20:10 -0000 The following reply was made to PR kern/154302; it has been noted by GNATS. From: Janne Snabb To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/154302: xn0: Error 2 parsing device/vif/0/mac [WORKAROUND] Date: Sat, 12 Feb 2011 09:12:06 +0000 (UTC) Justin T. Gibbs pointed out[1] that there is a simple workaround to this problem: Just remove 'type=ioemu' from the Xen domU's configuration. For example change: vif = [ 'type=ioemu, bridge=br0' ] ...to: vif = [ 'bridge=br0' ] After that the the mac node magically appears on the front-end side: # xenstore-read device/vif/0/mac 00:16:3e:69:3e:99 I think there is still a need for a patch though because not everyone (for examle VPS customers) have access to their domU's configuration. References: [1] http://lists.freebsd.org/pipermail/freebsd-xen/2011-February/000825.html -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/