From owner-freebsd-virtualization@FreeBSD.ORG Mon Jun 9 21:49:04 2008 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45467106567D for ; Mon, 9 Jun 2008 21:49:04 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from gritton.org (gritton.org [161.58.222.4]) by mx1.freebsd.org (Postfix) with ESMTP id 092248FC2A for ; Mon, 9 Jun 2008 21:49:03 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by gritton.org (8.13.6.20060614/8.13.6) with ESMTP id m59Ln0MY006243; Mon, 9 Jun 2008 15:49:00 -0600 (MDT) Message-ID: <484DA546.9060005@gritton.org> Date: Mon, 09 Jun 2008 15:48:54 -0600 From: James Gritton User-Agent: Thunderbird 2.0.0.9 (X11/20080228) MIME-Version: 1.0 To: Julian Elischer References: <484CC690.9020303@elischer.org> <20080609174826.Q83875@maildrop.int.zabbadoz.net> <484D8EDD.3040103@elischer.org> In-Reply-To: <484D8EDD.3040103@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.92.1/7416/Mon Jun 9 15:10:04 2008 on gritton.org X-Virus-Status: Clean Cc: freebsd-virtualization@freebsd.org Subject: Re: kinda headsup.. X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jun 2008 21:49:10 -0000 Could we have a list of what isn't expected to actually commit? So the scheduler stuff is out. Is that all of the struct vcpu? Parts of struct vprocg? I see some scheduling bits in both. Aside from vnet/vinet and the doomed scheduling bits, I see not much besides the hostname, domain name, and morphing symlinks. Are these staying? The hostname is already in jails ,and the domainname makes sense in my new jail framework - the morphing symlinks might be something best left for later. Ideally, for integration purposes, the vnet/vinet would hang off jails that have pretty much the same capability as the vimage structure, and then other bits could be added later. I don't want to worry about trying to integrate features that aren't in the final cut anyway. - Jamie Julian Elischer wrote: > ... > > This diff there includes experimental changes to virtualise things > like load average, and they will not be part of the commit. > so ignore anything that smells like "scheduler"