From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 3 14:28:30 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 457AE16A432 for ; Fri, 3 Mar 2006 14:28:30 +0000 (GMT) (envelope-from bohra@cs.rutgers.edu) Received: from dragon.rutgers.edu (dragon.rutgers.edu [128.6.25.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6561843D86 for ; Fri, 3 Mar 2006 14:28:17 +0000 (GMT) (envelope-from bohra@cs.rutgers.edu) X-Virus-Scanned: by dragon-cgpav-clamav-v1.3b Received: by dragon.rutgers.edu (CommuniGate Pro PIPE 5.0.7) with PIPE id 39407092; Fri, 03 Mar 2006 09:28:17 -0500 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on spamfilter1.rutgers.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,BAYES_50 autolearn=disabled version=3.1.0 Received: from [207.219.199.242] (account bohra HELO [192.168.0.97]) by dragon.rutgers.edu (CommuniGate Pro SMTP 5.0.7) with ESMTPSA id 39407086; Fri, 03 Mar 2006 09:28:00 -0500 From: Aniruddha Bohra To: kmacy@fsmware.com In-Reply-To: References: <79e2026f0602241120u77b4d043jca464a658bb0c0f7@mail.gmail.com> <44008135.1030901@samsco.org> <20060228175317.T19575@odysseus.silby.com> <20060228182139.O30130@thor.farley.org> <79e2026f0603021323h3ede49a6jc55ca816897847e@mail.gmail.com> Content-Type: text/plain Date: Fri, 03 Mar 2006 09:25:34 -0500 Message-Id: <1141395934.995.4.camel@freebsd-devel> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Ashok Shrestha , Scott Long , "=?ISO-8859-1?Q?Se=E1n?= C. Farley" , freebsd-hackers@freebsd.org Subject: Re: VMWARE GSX Port? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bohra@cs.rutgers.edu 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:28:30 -0000 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