From owner-freebsd-virtualization@FreeBSD.ORG Mon Jun 9 22:15:36 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 8EAE9106564A for ; Mon, 9 Jun 2008 22:15:36 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outZ.internet-mail-service.net (outz.internet-mail-service.net [216.240.47.249]) by mx1.freebsd.org (Postfix) with ESMTP id 78E4C8FC19 for ; Mon, 9 Jun 2008 22:15:36 +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 3881C24B6; Mon, 9 Jun 2008 15:15:36 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 064662D6010; Mon, 9 Jun 2008 15:15:35 -0700 (PDT) Message-ID: <484DAB87.6040706@elischer.org> Date: Mon, 09 Jun 2008 15:15:35 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: James Gritton References: <484CC690.9020303@elischer.org> <20080609174826.Q83875@maildrop.int.zabbadoz.net> <484D8EDD.3040103@elischer.org> <484DA546.9060005@gritton.org> In-Reply-To: <484DA546.9060005@gritton.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 22:15:36 -0000 James Gritton wrote: > 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. domain name and hostname both stay.. Hostname is tricky because both jail and vimage expect to change it.. though jail only really expects it to be virtualised to the user rather than REALLY VIRTUALISED. The morphing symlinks are an experimental feature. The verio guys have some work in that direction too that they want to work on.... hmmm that's not you is it? Loadavg etc. is not "out for ever" just "not in the first commit set." as they have not been extensively tested, and probably need more work. > > 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. the aim is that vimage and jail structures would merge. as the for "final cut", the schedule only covers initial commits of the vnet code, but once the framework is in place more functionality would be added. > > - 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"