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