From owner-freebsd-current@FreeBSD.ORG Mon May 4 17:32:47 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3787C106567A for ; Mon, 4 May 2009 17:32:47 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id 1C3CF8FC28 for ; Mon, 4 May 2009 17:32:46 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1D86922D6; Mon, 4 May 2009 10:32:47 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 55FFF2D63BE; Mon, 4 May 2009 10:32:46 -0700 (PDT) Message-ID: <49FF26C2.8080202@elischer.org> Date: Mon, 04 May 2009 10:32:50 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: "Paul B. Mahol" References: <49FC812B.2070305@elischer.org> <3a142e750905040553p48f6384aseb48c2067463ada4@mail.gmail.com> In-Reply-To: <3a142e750905040553p48f6384aseb48c2067463ada4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: VIMAGE status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 17:32:47 -0000 Paul B. Mahol wrote: > On 5/2/09, Julian Elischer wrote: >> The VIMAGE code is nearly all in the the kernel. >> >> One is now able to make VIMAGE kernels (add options VIMAGE) >> though they don't actually allow you to make multiple >> vimages instances yet.. >> >> The VIMAGE option enables all the low level changes needed >> throughout the kernel. >> >> The VIMAGE_GLOBALS option basically sets thing sback to how they were >> before. >> >> Having neither (the default) gives a kernel that is a kind of hybrid. >> >> The Hybrid state is what will go forward as 'NON-VIMAGE' mode >> and the VIMAGE_GLOBALS mode will probably go away in time as >> it complicates the code. >> >> The aim of this mail is to ask people to try add the VIMAGE option >> to their regular kernels and try use them as you woudl normally. >> You will not yet be able to use any new VIMAGE features but we >> should be fully compatible with previous kernels. >> >> Please report any concerns to the freebsd-virtualization@ mailing list. >> >> THEORETICALLY you should not see any changes in behaviour, however we >> have the following issues: >> >> * SCTP is not fully converted yet. add 'nooptions SCTP' for now if you >> are not using it yet. >> >> * An NFS (crash) issue was reported. This MAY have been fixed... >> >> >> Theory tells us that all three kernel options should behave about the >> same but if you do try this, and have any benchmarking facilities, >> it would be incredibly useful if you could let us know if you see any >> performance changes between the three. > > I'm experiencing strange 'netstat -r' output, perhaps I need to clean > /usr/obj/? (I dont have VIMAGE enabled) thanks if you do not have VIMAGE enabled then there should be no effect for you. I suggest you make sure that your userland and kernel are completely in sync. >