From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 10 09:30:30 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 8AE9B184; Mon, 10 Nov 2014 09:30:30 +0000 (UTC) Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F9F8750; Mon, 10 Nov 2014 09:30:30 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id im17so465395vcb.41 for ; Mon, 10 Nov 2014 01:30:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RTfCTeIcpIkN67rd52RVDCU/QbfGdmyV22ZFj+9h4jQ=; b=E8V6GfwXbQElZGTLKhpsedNtn6LxAZtT7hUuMqSsXlLitRYtibq9JB/r8YQYoBaSPN fxTDP1x/so5HrQaIrKuTuul+fOeYarJpGyzfYgAWOULsF70k5TLTjfksbsitMfAoD/03 ch+y0rUg5b4Z/DPfRwZ3neG62f7XNGuYhprjq/YFjt5NTeFnUgz0cMwxVNmYybB0gdtS K0tfsQjRnV3q72E6oOP/lC79Wn55dhl8B1yZGSi3K7EB4+w4W6t/ACr6K5Ja0nukK/To bilHIG87Y/7IgfLmh77nrktEV7DZqF37os4UBbV+bDCW2mDtKHkZCbPPkCrAkSqrumM2 LnVg== MIME-Version: 1.0 X-Received: by 10.52.9.37 with SMTP id w5mr1487067vda.38.1415611829334; Mon, 10 Nov 2014 01:30:29 -0800 (PST) Received: by 10.220.168.199 with HTTP; Mon, 10 Nov 2014 01:30:29 -0800 (PST) In-Reply-To: References: <20141012182551.002b3cc0a45a56d3f34e6174@yamagi.org> <3B4471A7-CDF4-440D-BDD8-3D5B2256B8DD@lists.zabbadoz.net> <7EAA2A23-06F9-44C9-A3E1-62AA37EE5CDA@lists.zabbadoz.net> Date: Mon, 10 Nov 2014 10:30:29 +0100 Message-ID: Subject: Re: Enabling VIMAGE by default for FreeBSD 11? From: Nikolay Denev To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 Cc: "Bjoern A. Zeeb" , freebsd-arch , "freebsd-virtualization@freebsd.org" , FreeBSD Net 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 09:30:30 -0000 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. --Nikolay