From owner-freebsd-arch@FreeBSD.ORG Thu Oct 11 17:22:58 2007 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BFA816A417 for ; Thu, 11 Oct 2007 17:22:58 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outU.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id 07D5513C48E for ; Thu, 11 Oct 2007 17:22:57 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 11 Oct 2007 10:22:56 -0700 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 4CC57126674; Thu, 11 Oct 2007 10:22:56 -0700 (PDT) Message-ID: <470E5BFB.4050903@elischer.org> Date: Thu, 11 Oct 2007 10:23:07 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: arch@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marko Zec Subject: kernel level virtualisation requirements. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 17:22:58 -0000 After PHK added jails, FreeBSD found a multitude of new applications, and they have served us well for quite some time. However since then Solaris and Linux have provided newer and more extensive virtualised abstractions, and it's probably time to think abut where we go from here. Marco Zec has been working on his network virtualisation, and Andre has spoken of what would be a subset of that, with policy based routing capacities (multiple routing tables etc.) I have been doing some private work on machines with multiple routing universes but that is not generally applicable. Some people have talked about cpu partition, resource sub partitioning and other aspects that could be considered to be part of presenting the appearance of many machines in one way or another. My reason for writing this is to see if as a group, we can come to a definition of what is needed, and how it can be organised. I'll start the ball rolling by stating that I'd like to see the vimage code merged with a general framework (it already has some aspects of this.. Marco has done a great job) and put in the new head branch. What I'd like to see is a bit of a 'a-la-carte' virtualisation ability. I'd like to be able to say.. I want to share the filesystem, and unix domain sockets but have a separate routing domain for my processes, or maybe just for some sockets. But someone else may want to have complete separation with everything up to and including separate userID spaces. My question to you, the reader, is: what aspects of virtualisation (the appearance of multiple instances of some resource) would you like to see in the system? Even a discussion as to how to frame this question is up for discussion. We don't even have a taxonomy to discus the issue. Julian