From owner-freebsd-xen@FreeBSD.ORG Sun Jan 6 00:48:42 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 A9990627 for ; Sun, 6 Jan 2013 00:48:42 +0000 (UTC) (envelope-from moto@kawasaki3.org) Received: from kawasaki3.org (blackpearl.kawasaki3.org [173.230.157.78]) by mx1.freebsd.org (Postfix) with ESMTP id 83285C19 for ; Sun, 6 Jan 2013 00:48:42 +0000 (UTC) Received: from localhost (s253.HtokyoFL10.vectant.ne.jp [222.228.92.253]) (Authenticated sender: moto) by kawasaki3.org (Postfix) with ESMTPSA id CF8A61CD42 for ; Sat, 5 Jan 2013 19:39:57 -0500 (EST) Date: Sun, 06 Jan 2013 09:39:41 +0900 (JST) Message-Id: <20130106.093941.323021822222343593.moto@kawasaki3.org> To: freebsd-xen@freebsd.org Subject: XENHVM hang-up w/ "network_alloc_rx_buffers: m_cljget failed" From: moto kawasaki X-Mailer: Mew version 6.5 on Emacs 24.2.50 / Mule 6.0 (HANACHIRUSATO) X-Face: )._4~w!_D$r6qNS0+; nS|]WNeI4f3o)QnH[ItB[esXuc$~hQ$.,?}$SnLe/[24Hao%^q/Is 'SJtZe#21h;7z;q+iyj[^%7\46.Gg-t7.px<}L-f_:P+6i4-a{DIL[ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Sun, 06 Jan 2013 00:48:42 -0000 Hello, Thank you very much for your effort to porting Xen to FreeBSD. I am so happy I can use FreeBSD instead of Linux on XenServer!! Today, I have encountered hang-ups as follows; - XenServer 6.1 * 3 hosts (HP DL360G7) - FreeBSD 9.0-RELEASE-p5 (customized XENHVM) * 2 VMs - Those VMs hang up with the following messages on console: network_alloc_rx_buffers: m_cjlget failed This message is repeatedly shown so quickly, and I cannot get login prompt. - During this issue, I cannot login via ssh over network, although TCP connection is established (I tried with telnet to ssh port). - I guess the trigger of this issue was something like broadcast storm, which was made by failed network configuration change. - This issue seems similar to exhausting mbuf(rx). Could you please advice me of countermeasure/prevention against this issue ? Also, I would like to know how to make it self-healing, I mean I want to make those VMs to recover automatically after the trigger had gone. Any suggestion/hint/reference is welcomed. Thank you very much. -- moto kawasaki