From owner-freebsd-emulation@FreeBSD.ORG Sun Jan 9 06:34:00 2011 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7830106566C for ; Sun, 9 Jan 2011 06:34:00 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6149D8FC0A for ; Sun, 9 Jan 2011 06:33:59 +0000 (UTC) Received: by wwf26 with SMTP id 26so18410020wwf.31 for ; Sat, 08 Jan 2011 22:33:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tNiNPPHWFlIpLpLWJhEyr4UEntGL4XA9FTGnWxt4fio=; b=TI4UHgJeJ/IftwGn9Tuyj8RhYF736CUy/CesOdBxgV/3csUm6qdwJ6FgpddAa/WNhH oOD/3Wt2YJf72bab7bMAguU8GxNcVRcwAVDVbbuhBI7rc6LiJlELt6Je90WMeBPWlynp GGYTPyHA0PFgBOXje/ipO/8xyEvTjQxNNuOww= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SaY6uPufy4mqGQa57nYWqatnVUdX+JdJmsOvrk3DkkZ7bJeNQ1gGIo1R7Y3HhAkxEj 5DCFctoapILLifdSDO7OeFDD3otBEcvOfZbKwqhBbcZ3e4pmNIwVOxxp3uvLep0txnnq Hje0hXJpHXgjNbzkZg1XqcjjdjoSAhMBaZRo8= MIME-Version: 1.0 Received: by 10.216.18.194 with SMTP id l44mr804028wel.87.1294554839118; Sat, 08 Jan 2011 22:33:59 -0800 (PST) Received: by 10.216.36.71 with HTTP; Sat, 8 Jan 2011 22:33:59 -0800 (PST) In-Reply-To: References: <20100418191752.GA72730@triton8.kn-bremen.de> <20110107194516.GA28544@triton8.kn-bremen.de> <20110107213643.GA32645@triton8.kn-bremen.de> Date: Sun, 9 Jan 2011 00:33:59 -0600 Message-ID: From: Brandon Gooch To: Xiaodong Yi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org, Juergen Lock Subject: Re: Testing Luvalley with FreeBSD as dom0 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2011 06:34:01 -0000 On Sun, Jan 9, 2011 at 12:01 AM, Xiaodong Yi wrote: > Hi, > > I confirm that I no longer have time for Luvalley. However, I will be > extreemly happy if anybody is willing to take over from me. > Especially, I quite agree to customize Luvalley for FreeBSD, through > it supports all kinds of Dom0 OSes. Howerver, I hope that the LIGHT > architecture of Luvalley could be kept. Maybe it is useful to patch > dom0 FreeBSD kernel (especially for interrupt handling), but it should > not be very complex. Part of the code comes from KVM, and I suggest to > keep flying with KVM to make sure that guest VMs work well. I believe that if serious effort were to be put forward by the FreeBSD developers to further develop the code, the result would need to be GPL and Linux free (or VERY close to it). This is an area of contention within the FreeBSD developer and user community, so it would need to be addressed. As the developer of Luvalley, do you have the ability to re-license the code using a BSD license? Are there too many technical issues with the code to do this? Juergen mentioned that bits of the code are based on (or pulled directly from?) Linux KVM. That probably wouldn't fly here... > Luvalley does boot and run on bare hardware. =A0But it does not taint > dom0 FreeBSD. Although the `non-root' mode dom0 FreeBSD kernel has > direct access to BIOS and hardware, Luvalley tries hard to coordinate > with it. For example, Luvalley traps the BIOS calls from the FreeBSD > kernel to report the modified E820 table. Another example is that > Luvalley uses NMI as the IPI interrupt to avoid conflict with BSD > kernel. And I also believe that simple patches could work if some > corners of FreeBSD kernel are tainted. > > Regards, and looking forward to the following news ... > > Xiaodong As am I... Thanks for chiming in Xiaodong! -Brandon