From owner-freebsd-xen@freebsd.org Fri Jan 20 16:49:27 2017 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D30CCCB9AE7; Fri, 20 Jan 2017 16:49:27 +0000 (UTC) (envelope-from prvs=18621f7f1=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04B321650; Fri, 20 Jan 2017 16:49:26 +0000 (UTC) (envelope-from prvs=18621f7f1=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.33,259,1477958400"; d="scan'208";a="39054257" Date: Fri, 20 Jan 2017 16:44:27 +0000 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: "Andrey V. Elsukov" CC: Trond =?iso-8859-1?Q?Endrest=F8l?= , SK , , "freebsd-stable@freebsd.org" , Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server Message-ID: <20170120164427.gghtafg2cfugnoro@dhcp-3-221.uk.xensource.com> References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To AMSPEX02CL02.citrite.net (10.69.22.126) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 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, 20 Jan 2017 16:49:27 -0000 On Fri, Jan 20, 2017 at 07:20:15PM +0300, Andrey V. Elsukov wrote: > On 20.01.2017 18:57, Trond Endrestøl wrote: > > > Here is the situation: > > > I have a VPS server from a well reputed provider (and they deserve the > > > reputation), running FreeBSD 11 stable x64 under Xen Full Virtualization > > > (HVM). I have the xn0 interface which is working fine. I intend to use VIMAGE, > > > so I compiled the kernel, added cloned_interface="bridge0" and restarted the > > > server. But as soon as I am attaching the xn0 to bridge0, the kernel is > > > panicking and the server restarting. > > > Any suggestion/pointer/test-instruction is highly appreciated. > > > > The code crashes at line 427 of sys/netinet/if_ether.c: > > > > ARPSTAT_INC(txrequests); > > > > See > > https://svnweb.freebsd.org/base/stable/11/sys/netinet/if_ether.c?view=annotate#l427 > > > > stable/11 has problems accounting the outgoing octets of any xn > > interface, although this isn't connected to your case. > > > > Just to rule out any uncertainty, try this patch: > > > > https://svnweb.freebsd.org/base?view=revision&revision=308126 > > > > See PR 213439, > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439 > > > > Note, I'm not a developer nor a committer, just a humble sysadmin. > > This problem is unrelated. ARP statistics is global and isn't related to > some specific interface. IMHO, the kernel panics due to missing VNET > context. As I see from the code in sys/dev/xen, it is not capable with > VIMAGE. I cannot really look into this right now due to lack of time, but I'm more than happy to review/apply patches in order to fix this. Roger.