From owner-freebsd-xen@freebsd.org Tue Jan 17 18:16:32 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 127EDCB4A89 for ; Tue, 17 Jan 2017 18:16:32 +0000 (UTC) (envelope-from prvs=183ec68f1=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 8AD6E107C for ; Tue, 17 Jan 2017 18:16:31 +0000 (UTC) (envelope-from prvs=183ec68f1=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.33,245,1477958400"; d="scan'208";a="38718357" Date: Tue, 17 Jan 2017 18:10:24 +0000 From: "roger.pau@citrix.com" To: Liuyingdong CC: "freebsd-xen@freebsd.org" , "Zhaojun (Euler)" , Suoben , chuzhaosong Subject: Re: I want to know how about these three patches for freebsd, Please let me know if you have any questions. Thanks. Message-ID: <20170117181024.7a6yoyiqdda3v2ey@dhcp-3-221.uk.xensource.com> References: <3655E9A8B903724782E1F75DCFD74E6B0122A0C12D@szxema506-mbs.china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <3655E9A8B903724782E1F75DCFD74E6B0122A0C12D@szxema506-mbs.china.huawei.com> User-Agent: NeoMutt/20170113 (1.7.2) X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) 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: Tue, 17 Jan 2017 18:16:32 -0000 On Fri, Jan 13, 2017 at 07:01:02AM +0000, Liuyingdong wrote: > Hello Roger, > I want to know how about these three patches for freebsd, Please let me know if you have any questions. > > these patches are listed as follows: > > l 0001 patch: I introduce suspend_cancel mechanism for frontend devices. > > l 0002 patch: I release all resources after hot unplug NICs. > > l 0003 patch: uvp-monitor need wait until stop_all_proc has finished. > > note: the uvp-monitor is a user space application in freebsd VM and it often reads or writes xenstore. Hello, I've already reviewed patches 0001 and 0002, please see: https://lists.freebsd.org/pipermail/freebsd-xen/2017-January/002931.html But you don't seem to have incorporated any of the feedback that I've provided. Roger. From owner-freebsd-xen@freebsd.org Fri Jan 20 14:48:44 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 02957CB8D86; Fri, 20 Jan 2017 14:48:44 +0000 (UTC) (envelope-from fbstable@cps-intl.org) Received: from mail3r.parlicentre.org (mail3r.parlicentre.org [199.48.129.20]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D339210CF; Fri, 20 Jan 2017 14:48:43 +0000 (UTC) (envelope-from fbstable@cps-intl.org) To: "freebsd-stable@freebsd.org" , freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org From: SK Message-ID: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> Date: Fri, 20 Jan 2017 14:26:18 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: fbstable@cps-intl.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail3r.parlicentre.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.1 Subject: FreeBSD 11 Stable on a Xen :: bridge0 crashing server X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail3r.parlicentre.org) 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 14:48:44 -0000 Dear List members Apologies for cross posting to two other lists -- was not sure which one is more appropriate for this, as it may be related to stable, xen or virtualization. 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. The provider confirmed that they found similar behaviour on a freshly installed/provisioned FreeBSD 11 x64 system. Further to that, the provider ran some tests, and what they are telling me is if they install/provision FreeBSD 10 x64, there is no problem with attaching bridge0 to xn0. Then they updated/upgraded that box to FreeBSD 11 x64, and that too worked when they attached bridge0 to xn0. However, they are yet to come back with my request to build a custom kernel with options VIMAGE and try it out. In the meanwhile, I took a crash dump and followed the FreeBSD handbook (not that it gave me much idea, I'm not a programmer nor am at that level of skillsets). The dump/debug is available at http://pastebin.com/XuWvJHUZ for anyone who is interested. Just wondering how to go about it. I do need to have bridge0 with xn0 and all the epairs I'm going to use for my jails. Any suggestion/pointer/test-instruction is highly appreciated. Best regards SK From owner-freebsd-xen@freebsd.org Fri Jan 20 15:58:06 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 EDB02CB86F9; Fri, 20 Jan 2017 15:58:06 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 969541123; Fri, 20 Jan 2017 15:58:06 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id v0KFvdjm011785 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Jan 2017 16:57:39 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id v0KFvd5V011782; Fri, 20 Jan 2017 16:57:39 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 20 Jan 2017 16:57:39 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: SK cc: "freebsd-stable@freebsd.org" , freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server In-Reply-To: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> Message-ID: References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 15:58:07 -0000 On Fri, 20 Jan 2017 14:26-0000, SK wrote: > Dear List members > > Apologies for cross posting to two other lists -- was not sure which one is > more appropriate for this, as it may be related to stable, xen or > virtualization. > > 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. > > The provider confirmed that they found similar behaviour on a freshly > installed/provisioned FreeBSD 11 x64 system. > > Further to that, the provider ran some tests, and what they are telling me is > if they install/provision FreeBSD 10 x64, there is no problem with attaching > bridge0 to xn0. Then they updated/upgraded that box to FreeBSD 11 x64, and > that too worked when they attached bridge0 to xn0. However, they are yet to > come back with my request to build a custom kernel with options VIMAGE and try > it out. > > In the meanwhile, I took a crash dump and followed the FreeBSD handbook (not > that it gave me much idea, I'm not a programmer nor am at that level of > skillsets). The dump/debug is available at http://pastebin.com/XuWvJHUZ for > anyone who is interested. > > Just wondering how to go about it. I do need to have bridge0 with xn0 and all > the epairs I'm going to use for my jails. > > 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. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-xen@freebsd.org Fri Jan 20 16:21:33 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 93421CB8FF3; Fri, 20 Jan 2017 16:21:33 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5j.cmail.yandex.net (forward5j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B5A312E1; Fri, 20 Jan 2017 16:21:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net [IPv6:2a02:6b8:0:f05::116]) by forward5j.cmail.yandex.net (Yandex) with ESMTP id 0A95C20F32; Fri, 20 Jan 2017 19:21:21 +0300 (MSK) Received: from smtp2h.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2h.mail.yandex.net (Yandex) with ESMTP id 3DA6F781EFF; Fri, 20 Jan 2017 19:21:16 +0300 (MSK) Received: by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ZEALLWeYek-LFAqU3Ot; Fri, 20 Jan 2017 19:21:16 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1484929276; bh=qjQsFsKYlrrzWyCmbX2jHPxwuT9tInBOK3z0M9jjPy4=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=iNi2xWRvP+vL/l/qJbVIATrEelATaY0D/1Yq3iVylEzJl/+wiNanXnc2uxCpN5Tjl 20L7dtZ1bsiYf9XwOD3+LFAArVppI9Wqtm43QX+rvKb3ebnMBKdN8cqa58Zbg1x+7F r254oCRswrEtq8M/PecXmKkSUmfeNGbc+DjmAefs= Authentication-Results: smtp2h.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server To: =?UTF-8?Q?Trond_Endrest=c3=b8l?= , SK References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> Cc: freebsd-xen@freebsd.org, "freebsd-stable@freebsd.org" , freebsd-virtualization@freebsd.org From: "Andrey V. Elsukov" Message-ID: Date: Fri, 20 Jan 2017 19:20:15 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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:21:33 -0000 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. -- WBR, Andrey V. Elsukov From owner-freebsd-xen@freebsd.org Fri Jan 20 16:43:51 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 6E543CB9805; Fri, 20 Jan 2017 16:43:51 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5348011CD; Fri, 20 Jan 2017 16:43:51 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cUcHK-000EFu-Ei; Fri, 20 Jan 2017 09:43:06 -0700 Date: Fri, 20 Jan 2017 09:43:06 -0700 From: The Doctor To: "Andrey V. Elsukov" Cc: Trond Endrest??l , SK , freebsd-xen@freebsd.org, "freebsd-stable@freebsd.org" , freebsd-virtualization@freebsd.org Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server Message-ID: <20170120164306.GA53685@doctor.nl2k.ab.ca> References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) 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:43:51 -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. > > -- > WBR, Andrey V. Elsukov Still we need to address this issue! Even here in FreeBSD-11 stable I see crashing of the bhyve. What I need to help you is what is needed for running gdb ../bhyve ../bhyve.core > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Birthdate 29 Jan 1969 Redhill Surrey England 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. From owner-freebsd-xen@freebsd.org Fri Jan 20 18:05:29 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 C04EDCB9649; Fri, 20 Jan 2017 18:05:29 +0000 (UTC) (envelope-from fbstable@cps-intl.org) Received: from mailer.parlicentre.org (mailer.parlicentre.org [199.48.132.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F61A1B26; Fri, 20 Jan 2017 18:05:29 +0000 (UTC) (envelope-from fbstable@cps-intl.org) To: The Doctor , "Andrey V. Elsukov" References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> <20170120164306.GA53685@doctor.nl2k.ab.ca> Cc: freebsd-xen@freebsd.org, "freebsd-stable@freebsd.org" , freebsd-virtualization@freebsd.org From: SK Message-ID: Date: Fri, 20 Jan 2017 17:36:37 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20170120164306.GA53685@doctor.nl2k.ab.ca> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: fbstable@cps-intl.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mailer.parlicentre.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailer.parlicentre.org) 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 18:05:29 -0000 On 20/01/2017 16:43, The Doctor wrote: > 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. >> >> -- >> WBR, Andrey V. Elsukov > Still we need to address this issue! > > Even here in FreeBSD-11 stable I see crashing > of the bhyve. > > What I need to help you is what is needed for running gdb ../bhyve ../bhyve.core > Apologies, but I might be missing something here. I am not trying to run bhyve, bhyve is not crashing. FreeBSD 11 in my case (FreeBSD testBox.test.domain 11.0-STABLE FreeBSD 11.0-STABLE #0 r312349: Fri Jan 20 12:29:17 GMT 2017 root@testBox.test.domain:/usr/obj/usr/src/sys/vnet-test amd64) is running on a Xen HVM, and as I am trying to attach bridge0 to any interface (either xn0, or epair0a, or so on), the server is crashing and rebooting. I had the line ifconfig_bridge0="addm xn0 addm epair0a up" on the /etc/rc.conf , and the server went into an infinite crash-reboot loop. What I would like to have, if possible, is running FreeBSD 11 stable on the server, use vnet/vimage for my jails so I can isolate each of them from one another. Currently I am building world with the patch suggested by Trond (started that before I read the mail from Andrey). But if that is unlikely to bring a solution, that would mean most people on VPS with jails that are using Xen are going to suffer from any upgrade to 11 (or having new servers running 11) -- which is definitely undesirable. If anyone would like me to run further test on the box, please let me know what you'd like me to run, and I can come back with the response. Having a reliable/stable solution is the objective from my end. Thanks to all for your suggestions/comments. Regards SK From owner-freebsd-xen@freebsd.org Fri Jan 20 18:13:07 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 28077CB9971; Fri, 20 Jan 2017 18:13:07 +0000 (UTC) (envelope-from fbstable@cps-intl.org) Received: from mailer.parlicentre.org (mailer.parlicentre.org [199.48.132.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E8A41099; Fri, 20 Jan 2017 18:13:06 +0000 (UTC) (envelope-from fbstable@cps-intl.org) From: SK To: freebsd-stable@freebsd.org, freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> <20170120164427.gghtafg2cfugnoro@dhcp-3-221.uk.xensource.com> Message-ID: <6cf1e470-f218-8c7a-bf94-9dcbf3320eef@cps-intl.org> Date: Fri, 20 Jan 2017 18:10:48 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20170120164427.gghtafg2cfugnoro@dhcp-3-221.uk.xensource.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-SA-Exim-Mail-From: fbstable@cps-intl.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mailer.parlicentre.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server :: &ro X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailer.parlicentre.org) 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 18:13:07 -0000 On 20/01/2017 16:44, Roger Pau Monné wrote: > 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. > Further to my previous, since the provider of the VPS confirmed that they could run FreeBSD 10 and use bridge without any issue, I thought I'd have a look. The section from my crash-debug 0xffffffff80c2dd93 is in arprequest (/usr/src/sys/netinet/if_ether.c:427). 422 ro.ro_flags = 0; 423 424 m->m_flags |= M_BCAST; 425 m_clrprotoflags(m); /* Avoid confusing lower layers. */ 426 (*ifp->if_output)(ifp, m, &sa, &ro); 427 ARPSTAT_INC(txrequests); 428 } 429 430 I compared the file (if_ether.c) from 10, and it seems that the line 426 is different -- it contains NULL instead of &ro at the end. I did nto see any ro.* (right before this section) on the file in 10 either. Could this be significant? Thanks and regards SK From owner-freebsd-xen@freebsd.org Fri Jan 20 18:39:49 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 51BABCB9356; Fri, 20 Jan 2017 18:39:49 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36BEE1147; Fri, 20 Jan 2017 18:39:49 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cUe5S-000PAF-Ia; Fri, 20 Jan 2017 11:38:58 -0700 Date: Fri, 20 Jan 2017 11:38:58 -0700 From: The Doctor To: SK Cc: "Andrey V. Elsukov" , freebsd-xen@freebsd.org, "freebsd-stable@freebsd.org" , freebsd-virtualization@freebsd.org Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server Message-ID: <20170120183858.GB93874@doctor.nl2k.ab.ca> References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> <20170120164306.GA53685@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) 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 18:39:49 -0000 On Fri, Jan 20, 2017 at 05:36:37PM +0000, SK wrote: > On 20/01/2017 16:43, The Doctor wrote: > > 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. > >> > >> -- > >> WBR, Andrey V. Elsukov > > Still we need to address this issue! > > > > Even here in FreeBSD-11 stable I see crashing > > of the bhyve. > > > > What I need to help you is what is needed for running gdb ../bhyve ../bhyve.core > > > Apologies, but I might be missing something here. I am not trying to run > bhyve, bhyve is not crashing. FreeBSD 11 in my case (FreeBSD > testBox.test.domain 11.0-STABLE FreeBSD 11.0-STABLE #0 r312349: Fri Jan > 20 12:29:17 GMT 2017 > root@testBox.test.domain:/usr/obj/usr/src/sys/vnet-test amd64) is > running on a Xen HVM, and as I am trying to attach bridge0 to any > interface (either xn0, or epair0a, or so on), the server is crashing and > rebooting. I had the line ifconfig_bridge0="addm xn0 addm epair0a up" on > the /etc/rc.conf , and the server went into an infinite crash-reboot loop. > > What I would like to have, if possible, is running FreeBSD 11 stable on > the server, use vnet/vimage for my jails so I can isolate each of them > from one another. > > Currently I am building world with the patch suggested by Trond (started > that before I read the mail from Andrey). But if that is unlikely to > bring a solution, that would mean most people on VPS with jails that are > using Xen are going to suffer from any upgrade to 11 (or having new > servers running 11) -- which is definitely undesirable. > > If anyone would like me to run further test on the box, please let me > know what you'd like me to run, and I can come back with the response. > Having a reliable/stable solution is the objective from my end. > > Thanks to all for your suggestions/comments. > > Regards > SK Well in my case using gdb /usr/sbin/bhyve /path/to/bhyve.core I get GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `bhyve'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libvmmapi.so.5...Reading symbols from /usr/lib/debug//usr/lib/libvmmapi.so.5.debug...done. done. Loaded symbols for /usr/lib/libvmmapi.so.5 Reading symbols from /lib/libmd.so.6...Reading symbols from /usr/lib/debug//lib/libmd.so.6.debug...done. done. Loaded symbols for /lib/libmd.so.6 Reading symbols from /lib/libz.so.6...Reading symbols from /usr/lib/debug//lib/libz.so.6.debug...done. done. Loaded symbols for /lib/libz.so.6 Reading symbols from /lib/libthr.so.3...Reading symbols from /usr/lib/debug//lib/libthr.so.3.debug...done. done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...Reading symbols from /usr/lib/debug//lib/libc.so.7.debug...done. done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/libutil.so.9...Reading symbols from /usr/lib/debug//lib/libutil.so.9.debug...done. done. Loaded symbols for /lib/libutil.so.9 Reading symbols from /libexec/ld-elf.so.1...Reading symbols from /usr/lib/debug//libexec/ld-elf.so.1.debug...done. done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x000000080119755a in thr_kill () from /lib/libc.so.7 [New Thread 945218000 (LWP 102104/)] [New Thread 801a77400 (LWP 102102/)] [New Thread 801a76a00 (LWP 102087/)] [New Thread 801a76500 (LWP 102086/)] [New Thread 801a76000 (LWP 102085/)] [New Thread 801a1cb00 (LWP 102084/)] [New Thread 801a1c600 (LWP 102082/)] [New Thread 801a1c100 (LWP 102081/)] [New Thread 801a1bc00 (LWP 102080/)] [New Thread 801a1b700 (LWP 102079/)] [New Thread 801a1b200 (LWP 102078/)] [New Thread 801a1ad00 (LWP 102070/)] [New Thread 801a1a800 (LWP 102069/)] [New Thread 801a1a300 (LWP 102068/)] [New Thread 801a19e00 (LWP 102067/)] [New Thread 801a19900 (LWP 101469/)] [New Thread 801a19400 (LWP 100683/)] [New Thread 801a18f00 (LWP 100671/)] [New Thread 801a18a00 (LWP 100667/)] [New Thread 801a18500 (LWP 100666/)] [New Thread 801a18000 (LWP 100989/)] (Gdb) Where do I go from here? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Birthdate 29 Jan 1969 Redhill Surrey England From owner-freebsd-xen@freebsd.org Fri Jan 20 19:57:25 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 47094CBA315; Fri, 20 Jan 2017 19:57:25 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3o.cmail.yandex.net (forward3o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::288]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E39711974; Fri, 20 Jan 2017 19:57:24 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:7]) by forward3o.cmail.yandex.net (Yandex) with ESMTP id 49C1320BFF; Fri, 20 Jan 2017 22:57:12 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 4D2451A80049; Fri, 20 Jan 2017 22:57:09 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Z2fg7FXzGO-v9sOVqfs; Fri, 20 Jan 2017 22:57:09 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1484942229; bh=kkbBrp+NSfTopa4x5yCCIs6QMRgO+FcR3k0s7/LPA/Y=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Q0QbViV53FgWeJvrLkksKXr7lbpWfiiV5dkUOg8OMaj7ITpmXxQ9TWYRmQHxLy3/X wz3nI9S9kkWeSEnmtk37/2h7jk2QQlyZH86t4L23gUKL4Lt3DMOTu07uLyAYKsXOIs UqqprEPHOPjT8KKI9yXp1wH+r96X7G8KBX0VEMR8= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: FreeBSD 11 Stable on a Xen :: bridge0 crashing server :: &ro To: SK , freebsd-stable@freebsd.org, freebsd-xen@freebsd.org, freebsd-virtualization@freebsd.org, "Bjoern A. Zeeb" References: <7c06aea6-0b10-e9c0-d750-f42d4a406258@cps-intl.org> <20170120164427.gghtafg2cfugnoro@dhcp-3-221.uk.xensource.com> <6cf1e470-f218-8c7a-bf94-9dcbf3320eef@cps-intl.org> From: "Andrey V. Elsukov" Message-ID: <7df0bac1-6f7c-c332-e65c-e5ec7a6f9112@yandex.ru> Date: Fri, 20 Jan 2017 22:56:08 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <6cf1e470-f218-8c7a-bf94-9dcbf3320eef@cps-intl.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 19:57:25 -0000 On 20.01.2017 21:10, SK wrote: >>>> 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. >> > Further to my previous, since the provider of the VPS confirmed that > they could run FreeBSD 10 and use bridge without any issue, I thought > I'd have a look. The section from my crash-debug > 0xffffffff80c2dd93 is in arprequest (/usr/src/sys/netinet/if_ether.c:427). > 422 ro.ro_flags = 0; > 423 > 424 m->m_flags |= M_BCAST; > 425 m_clrprotoflags(m); /* Avoid confusing lower layers. */ > 426 (*ifp->if_output)(ifp, m, &sa, &ro); > 427 ARPSTAT_INC(txrequests); > 428 } > 429 > 430 Well, as I said, there is no VNET support in the sys/dev/xen. It may work without problems even if you have compiled it with VIMAGE enabled. But it will crash just after you try to start some VNET-jail. It is just not implemented yet. -- WBR, Andrey V. Elsukov