From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 3 14:42:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FE2516A420 for ; Fri, 3 Mar 2006 14:42:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23ED643D4C for ; Fri, 3 Mar 2006 14:41:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k23Ef6qg078043; Fri, 3 Mar 2006 07:41:06 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44085588.1080909@samsco.org> Date: Fri, 03 Mar 2006 07:41:12 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: bohra@cs.rutgers.edu References: <79e2026f0602241120u77b4d043jca464a658bb0c0f7@mail.gmail.com> <44008135.1030901@samsco.org> <20060228175317.T19575@odysseus.silby.com> <20060228182139.O30130@thor.farley.org> <79e2026f0603021323h3ede49a6jc55ca816897847e@mail.gmail.com> <1141395934.995.4.camel@freebsd-devel> In-Reply-To: <1141395934.995.4.camel@freebsd-devel> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: =?ISO-8859-1?Q?=22Se=E1n_=5C=22C=2E_Far?=, Ashok Shrestha , kmacy@fsmware.com, =?ISO-8859-1?Q?ley=5C=22=22?= , freebsd-hackers@freebsd.org Subject: Re: VMWARE GSX Port? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2006 14:42:02 -0000 Aniruddha Bohra wrote: > On Thu, 2006-03-02 at 13:28 -0800, Kip Macy wrote: > >>-CURRENT runs on 3.0 as a domU. There is partial dom0 support. The >>changes have not gone back into the mainline because xenbus is >>extremely difficult to integrate cleanly. You can check on the state >>of the xen3 branch in perforce. > > > At several places the "difficulties" are mentioned. Is there some place > that these are listed or discussed in more detail? > > Thanks > Aniruddha > > The difficulty is that Xen uses a Mach-like message passing system to communicate information like DomU configuration. This requires kernel threads to be operational early on in the startup of the DomU kernel, much earlier than what FreeBSD allows. My attempts so far to allow xenbus to synchronously retrieve its devce configuration instead of relying on asynchronous messages has been unsuccessfull. Scott