From owner-freebsd-virtualization@FreeBSD.ORG Mon Jun 9 22:20:53 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 16B351065675 for ; Mon, 9 Jun 2008 22:20:53 +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 B9BA18FC15 for ; Mon, 9 Jun 2008 22:20:52 +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 m59MKoQD009821; Mon, 9 Jun 2008 16:20:51 -0600 (MDT) Message-ID: <484DACBD.50109@gritton.org> Date: Mon, 09 Jun 2008 16:20:45 -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> <484DA546.9060005@gritton.org> <484DAB87.6040706@elischer.org> In-Reply-To: <484DAB87.6040706@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 22:20:53 -0000 Julian Elischer wrote: > 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. I notice there are some differences between the two approaches, and plan to keep the hostname as virtualized as possible. But really, the differences are few and easily merged. > 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? Yeah, could be. So while it's a feature I understand and like, I still prefer it remain for later. > 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. "Final cut" was a poor choice of words - I too am talking about the first commit that covers the vnet code. - Jamie