From owner-freebsd-xen@FreeBSD.ORG Mon Jun 3 11:06:56 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 28CB760A for ; Mon, 3 Jun 2013 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 02750144B for ; Mon, 3 Jun 2013 11:06:56 +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 r53B6tAs015244 for ; Mon, 3 Jun 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r53B6tg9015242 for freebsd-xen@FreeBSD.org; Mon, 3 Jun 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Jun 2013 11:06:55 GMT Message-Id: <201306031106.r53B6tg9015242@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, 03 Jun 2013 11:06:56 -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/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 35 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Jun 3 21:07:47 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9EC2F681 for ; Mon, 3 Jun 2013 21:07:47 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id 4670F17A9 for ; Mon, 3 Jun 2013 21:07:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpapi; bh=JcZFBCEfm+rvVb5vXYVmTA ih+WA=; b=dXPMcQZ/E/V663NQym5hACfqWlKxtDfofwKVB8beKC1rd9GDiYUbpa KVTALtwIrEab6LbcG4mHe3tebv8ayaTDijv/dX8G9MBtq+FDJV7ocMjl5DdTtoIF JuLQIu4LWCeyJyjbSo/lEc1SQwuH0ZVJKQ9yRVT8p/bDEruQBhJqE= Received: by 10.42.83.46 with SMTP id filterdell-006.4796.51AD05A21 Mon, 03 Jun 2013 21:07:46 +0000 (GMT) Received: from mail.tarsnap.com (unknown [10.60.208.13]) by mi1 (SG) with ESMTP id 13f0bde008a.7323.fa16c6 for ; Mon, 03 Jun 2013 16:07:45 -0500 (CST) Received: (qmail 70826 invoked from network); 3 Jun 2013 21:07:44 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 3 Jun 2013 21:07:44 -0000 Received: (qmail 48814 invoked from network); 3 Jun 2013 21:06:57 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 3 Jun 2013 21:06:57 -0000 Message-ID: <51AD0571.90007@freebsd.org> Date: Mon, 03 Jun 2013 14:06:57 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130524 Thunderbird/17.0.6 MIME-Version: 1.0 To: Andre Oppermann Subject: Re: svn commit: r251297 - head/sys/dev/xen/netfront References: <201306031300.r53D0XUx092178@svn.freebsd.org> In-Reply-To: <201306031300.r53D0XUx092178@svn.freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SG-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/Iwt4ABf+0rZIspu32RID0WSz0IbZQ8X8pda2+fFbCDeKNH93OTupw7kQVJWhN//CjNIqWGOY9r0sh/wEGmUx5w1NuJxSRjC/Z881SwwRKFkUg== 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, 03 Jun 2013 21:07:47 -0000 On 06/03/13 06:00, Andre Oppermann wrote: > Log: > Specify a maximum TSO length limiting the segment chain to what the > Xen host side can handle after defragmentation. > > This prevents the driver from throwing away too long TSO chains and > improves the performance on Amazon AWS instances with 10GigE virtual > interfaces to the normally expected throughput. Thanks! For the benefit of the list: This (and the r251296, which provides the network stack infrastructure which this commit uses) was the last of the "make FreeBSD behave well in Amazon EC2" patches I've been carrying around (and building into my EC2 images) for the past two years. Now the only step remaining to make FreeBSD/EC2 pure "straight off the RELEASE ISO" FreeBSD is to get Xen HVM functionality into GENERIC. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Fri Jun 7 20:27:09 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A7917F33; Fri, 7 Jun 2013 20:27:09 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.167]) by mx1.freebsd.org (Postfix) with ESMTP id 0EE8112ED; Fri, 7 Jun 2013 20:27:09 +0000 (UTC) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id D761634360; Fri, 7 Jun 2013 16:27:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXcRHTm4KqNx; Fri, 7 Jun 2013 16:27:07 -0400 (EDT) Received: from daemon.localdomain (daemon.egr.msu.edu [35.9.44.65]) by mail.egr.msu.edu (Postfix) with ESMTP id B31E13435A; Fri, 7 Jun 2013 16:27:07 -0400 (EDT) Received: by daemon.localdomain (Postfix, from userid 21281) id ACF5E11AF59; Fri, 7 Jun 2013 16:27:07 -0400 (EDT) Date: Fri, 7 Jun 2013 16:27:07 -0400 From: Adam McDougall To: Colin Percival Subject: Re: svn commit: r251297 - head/sys/dev/xen/netfront Message-ID: <20130607202707.GB4240@egr.msu.edu> References: <201306031300.r53D0XUx092178@svn.freebsd.org> <51AD0571.90007@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51AD0571.90007@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) 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: Fri, 07 Jun 2013 20:27:09 -0000 On Mon, Jun 03, 2013 at 02:06:57PM -0700, Colin Percival wrote: On 06/03/13 06:00, Andre Oppermann wrote: > Log: > Specify a maximum TSO length limiting the segment chain to what the > Xen host side can handle after defragmentation. > > This prevents the driver from throwing away too long TSO chains and > improves the performance on Amazon AWS instances with 10GigE virtual > interfaces to the normally expected throughput. Thanks! For the benefit of the list: This (and the r251296, which provides the network stack infrastructure which this commit uses) was the last of the "make FreeBSD behave well in Amazon EC2" patches I've been carrying around (and building into my EC2 images) for the past two years. Now the only step remaining to make FreeBSD/EC2 pure "straight off the RELEASE ISO" FreeBSD is to get Xen HVM functionality into GENERIC. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid Is it possible to turn it into a boot time tunable in case XENHVM puts a system at a disadvantage? I'm specifically thinking of some XENHVM environments under XenServer and related products that aren't currently compat with having a virtual cdrom due to a bug. Removing the virtual cdrom drive is a workaround but that makes it a lot harder to boot from a RELEASE ISO :) Apologies if it already has a tunable, but I did some searching and could not locate it. It was desirable too back when a XENHVM kernel would panic on bare hw but that was fixed a while ago.