Date: Fri, 03 Mar 2006 07:41:12 -0700 From: Scott Long <scottl@samsco.org> To: bohra@cs.rutgers.edu Cc: =?ISO-8859-1?Q?=22Se=E1n_=5C=22C=2E_Far?=, Ashok Shrestha <ashok.shrestha@gmail.com>, kmacy@fsmware.com, =?ISO-8859-1?Q?ley=5C=22=22?= <sean-freebsd@farley.org>, freebsd-hackers@freebsd.org Subject: Re: VMWARE GSX Port? Message-ID: <44085588.1080909@samsco.org> In-Reply-To: <1141395934.995.4.camel@freebsd-devel> References: <79e2026f0602241120u77b4d043jca464a658bb0c0f7@mail.gmail.com> <44008135.1030901@samsco.org> <20060228175317.T19575@odysseus.silby.com> <20060228182139.O30130@thor.farley.org> <79e2026f0603021323h3ede49a6jc55ca816897847e@mail.gmail.com> <b1fa29170603021328m530fdca9h5dde855947370841@mail.gmail.com> <1141395934.995.4.camel@freebsd-devel>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44085588.1080909>