From owner-freebsd-virtualization@FreeBSD.ORG Mon May 19 13:56:05 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7157EF19 for ; Mon, 19 May 2014 13:56:05 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (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 4B30D2EAB for ; Mon, 19 May 2014 13:56:05 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 423F1B986; Mon, 19 May 2014 09:56:04 -0400 (EDT) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: bhyve + freenas + vimage jails Date: Mon, 19 May 2014 09:53:02 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201405190953.02807.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 May 2014 09:56:04 -0400 (EDT) Cc: Joe Maloney X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 13:56:05 -0000 On Monday, May 19, 2014 12:19:27 am Joe Maloney wrote: > I've been noticing that when VIMAGE jails are created in FreeNAS within a > bhyve VM the system VM kernel panics quite a bit. > > I'm running 11 Current updated as of today. I've tried with options VIMAGE > turned on and with a GENERIC kernel and see the same result either way. > Sometimes it works, sometimes it doesn't. Not really a huge deal as I've > just been testing for fun but if I will provide logs if anyone would like > to see. I would just need to know how to pull them. You can start with the /var/crash/core.txt.N file which includes the kernel messages and kgdb stacktrace (assuming you are getting crashdumps) -- John Baldwin