From owner-freebsd-jail@FreeBSD.ORG Wed Feb 1 03:28:57 2012 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5730E106566C for ; Wed, 1 Feb 2012 03:28:57 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1AC528FC13 for ; Wed, 1 Feb 2012 03:28:56 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa07 [127.0.0.1]) by ltcfislmsgpa07.fnfis.com (8.14.4/8.14.4) with SMTP id q113RVl8004957; Tue, 31 Jan 2012 21:28:56 -0600 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com with ESMTP id 12pu1ygd9w-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 31 Jan 2012 21:28:56 -0600 Received: from [10.0.0.102] (10.14.152.28) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 31 Jan 2012 21:28:55 -0600 MIME-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: <20120131213131.534682f2@poseidon.unh.edu> Date: Tue, 31 Jan 2012 19:28:53 -0800 Message-ID: References: <20120131213131.534682f2@poseidon.unh.edu> To: Alex X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.211, 0.0.0000 definitions=2012-02-01_01:2012-01-31, 2012-02-01, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-jail@freebsd.org Subject: Re: Instability with VIMAGE X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 03:28:57 -0000 On Jan 31, 2012, at 6:31 PM, Alex wrote: > Hello. I am running FreeBSD 9.0-RELEASE, and I am having many > instability issues. Starting a jail and adding an epair works fine > (sort of), but if I were to walk away and come back a few hours later, > the server would be offline and I would need to have someone locally > reboot it. In response, I removed SCTP from the kernel to see if that > would alleviate the problems, but it did not. I tried to terminate a > jail via `jail -r ', but I received this message: >=20 > mybox# 30 second watchdog timeout expired. Shutdown terminated. > Tue Jan 31 05:46:47 UTC 2012 > Write failed: Broken pipe >=20 > ...and at this point I would need someone to reboot the server. >=20 It's not really said here whether you're reclaiming the vnet interface with= the "-vnet" flag to ifconfig(8) _before_ shutting down the jail, but it's = generally not advised to rip the rug out from under the interface. At least in 8.1, the vnet doesn't automatically re-appear in the base host,= and if you rip the rug out from under the interface by shutting down the j= ail with "jail -r", then you have to manually reclaim the interface by usin= g the numerical jail-id and the "-vnet" parameter to ifconfig(8). > Am I doing something wrong? Should I avoid using VIMAGE due to its > inherent instability? I don't know about "inherent instability", we're using it every day quite s= tably with dozens of vimages. However, we're not using epair, but rather ne= tgraph. I wrote a boot script for setting up netgraph bridges. If you like,= you have a read (and download an easy-to-install FreeBSD package to try it= out)... http://druidbsd.sf.net/vimage.shtml http://druidbsd.sf.net/download.shtml My boot script supports both simple "vnet" usage (and makes sure to return = the interface to the base host, no matter what), as well as the more compli= cated netgraph(4) bridging. Be sure to read-up on the first link. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.