From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 10 14:14:34 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4E422F2; Mon, 10 Nov 2014 14:14:33 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AB13098F; Mon, 10 Nov 2014 14:14:33 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sAAEEP7R053048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 10 Nov 2014 06:14:28 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <5460C839.7060404@freebsd.org> Date: Mon, 10 Nov 2014 22:14:17 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Nikolay Denev , Craig Rodrigues Subject: Re: Enabling VIMAGE by default for FreeBSD 11? References: <20141012182551.002b3cc0a45a56d3f34e6174@yamagi.org> <3B4471A7-CDF4-440D-BDD8-3D5B2256B8DD@lists.zabbadoz.net> <7EAA2A23-06F9-44C9-A3E1-62AA37EE5CDA@lists.zabbadoz.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Nov 2014 14:14:34 -0000 On 11/10/14, 5:30 PM, Nikolay Denev wrote: > On Mon, Nov 10, 2014 at 2:33 AM, Craig Rodrigues wrote: >> On Sun, Oct 12, 2014 at 6:07 PM, Bjoern A. Zeeb < >> bzeeb-lists@lists.zabbadoz.net> wrote: >> >>> >>>> Can you provide a pointer to your Perforce branch? >>> //depot/user/bz/vimage/src/... >>> >>> >> Hi, >> >> Since I am more familiar with git than Perforce, I converted >> your Perforce branch to git and put it on github: >> >> https://github.com/rodrigc/bz-vimage >> >> I took a look at the history of that branch, and it looks like you >> merged quite a lot of changes in this branch back to FreeBSD. >> There were a few places where it looks like the code in your branch >> diverged from FreeBSD (in carp area, for example). >> >> Offhand, can you remember any VIMAGE related memory leaks >> you might have fixed in this branch which you did not merge back? >> >> This one looks pretty simple by removing UMA_ZONE_NOFREE in a few >> places: >> >> https://github.com/rodrigc/bz-vimage/commit/ebe7e4c5e7e5b3dbfc442a25f10ca8681c605c89 >> >> >> In this one, you added dom_pr_register() and dom_pr_unregister() hooks: >> >> https://github.com/rodrigc/bz-vimage/commit/a1d5c8bc2f4484e58594ca8fad793aa339a5ef29 >> >> but I'm not sure if you wanted to merge this back to FreeBSD or not. >> >> Can you think of anything else in this branch that we need for VIMAGE? >> >> Thanks. >> >> -- >> Craig >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > I haven't checked if this is fixed in CURRENT, but at least on > 10.0-STABLE r270295M, > gif(4) does not seem to play well with VIMAGE. > > I've just noticed that gif(4) interface unit numbers seem to be unique > per machine, regardless of the vnet (I guess unit numbering not > properly virtualized), > so that if I create gif0 in one vnet jail and try the same in another > vnet jail I get "ifconfig: SIOCIFCREATE2: File exists" > > What's even worse is that once the jail is destroyed, the gif(4) > tunnel interface disappears from the system (no longer shows in > ifconfig), but you can't reuse the unit number, so > I continue to get SIOCIFCREATE2: File exists for gif0 on the host or > other vnet jails. yes there are some parts of the system where the design is not compatible with virtualization. for example.. if a single /dev entry controls stuff.. which kind of complicates things.. > > --Nikolay > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" >