Date: Sun, 30 Oct 2016 14:57:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Message-ID: <bug-213896-9824-TqWHpatoHQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213896-9824@https.bugs.freebsd.org/bugzilla/> References: <bug-213896-9824@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 Joe Barbish <qjail1@a1poweruser.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qjail1@a1poweruser.com --- Comment #1 from Joe Barbish <qjail1@a1poweruser.com> --- I am running FreeBSD 11-RELEASE-p1 installed from scratch using cdrom.iso. I have tested ipfw on the host and in a vimage jail with out any problems. = My custom kernel only has vimage compiled in. The host is running ipfw without usimg DUMMYNET, IPDIVERT or IPFIREWALL_NAT. The vimage jail is also running ipfw without using those same functions. The only problem with ipfw is the vimage jails ipfw log messages get intermingled into the host's ipfw log file. I also tested with=20 options VIMAGE options IPFIREWALL options IPFIREWALL_NAT # ipfw kernel nat support options IPDIVERT # divert sockets options LIBALIAS # required by IPFIREWALL_NAT compiled into the kernel and the host system booted fine with ipfw on the h= ost and the vimage jail worked the same as NOT compiling in ipfw. Did not test = ipfw using using those "functions listed above" on the host or vimage jail.=20 The only reason to compile ipfw into the kernel is if the host is not runni= ng ipfw. A vimage jail does not kldload modules on first reference like the ho= st does so you have to compile them into the kernel. An alternative is to configure your vimage jail's jail.conf with a exec.prestart option to kldlo= ad the ipfw modules used by the vimage jail.=20 I didn't get any error messages from installkernel task during the vimage kernel compile. My guess is nospam@ofloo.net has problem with his upgrade to 11.0 or had existing kernel compile problems before the upgrade which left = his updated system messed up.=20 Suggest a install of 11.0 to a blank disk will correct this problem. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213896-9824-TqWHpatoHQ>