Date: Sun, 9 Jan 2011 14:01:43 +0800 From: Xiaodong Yi <xdong.yi@gmail.com> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: freebsd-emulation@freebsd.org Subject: Re: Testing Luvalley with FreeBSD as dom0 Message-ID: <AANLkTi=2Nn8xeKudxb2uSR=aLx0GW43gVPCdL-=hjP7z@mail.gmail.com> In-Reply-To: <20110107213643.GA32645@triton8.kn-bremen.de> References: <20100418191752.GA72730@triton8.kn-bremen.de> <w2r3b0605b31004181554tb90de59u6df8ebd5b1206caa@mail.gmail.com> <AANLkTi=nhk%2BeCG6kbe4LfeaTQWkKaVcr%2BRx2LrKparDO@mail.gmail.com> <20110107194516.GA28544@triton8.kn-bremen.de> <AANLkTikvP8SezKEZYSUimaj3u8fkk2Vw6-aY09KV=RF3@mail.gmail.com> <20110107213643.GA32645@triton8.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Luvalley does boot and run on bare hardware. But 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 2011/1/8 Juergen Lock <nox@jelal.kn-bremen.de>: > On Fri, Jan 07, 2011 at 02:02:57PM -0600, Brandon Gooch wrote: >> On Fri, Jan 7, 2011 at 1:45 PM, Juergen Lock <nox@jelal.kn-bremen.de> wr= ote: >> > On Mon, Jan 03, 2011 at 08:00:01PM -0600, Adam Vande More wrote: >> >> On Sun, Apr 18, 2010 at 5:54 PM, Xiaodong Yi <xdong.yi@gmail.com> wro= te: >> >> >> >> > I am very glad that Juergen introduced Luvalley to the FreeBSD >> >> > society. We hope you like the idea of it. And we will be much more >> >> > pleased for the feedbacks. Luvally now is only experimental and may= be >> >> > not stable or low performance. But I will continue working to impro= ve >> >> > it. >> >> > >> >> >> >> Just wondering if there's been any progress here? =A0Is it still unde= r >> >> development on FreeBSD? >> > >> > I probably should have posted here when Xiaodong Yi told me a while >> > ago that he no longer has time for Luvalley. =A0(That mail was some >> > time after I asked him about his last sourceforge release which I >> > couldn't get to run on my hw.) >> > >> > =A0So I guess you can say this project is now looking for new >> > `volunteers'... >> > >> > =A0:/ >> > =A0 =A0 =A0 =A0Juergen >> >> Could Luvalley become BSD licensed? > > I think parts of its code are based on the Linux kvm kernel bits > so I guess those authors would have to agree too besides the > Luvalley author... =A0(The linux kernel is only gplv2 tho not gplv3 > and it seems Linus wants it to stay that way.) > > =A0Oh and also IANAL but since the Luvalley `kernel' (hypervisor) > runs on bare metal and boots any dom0 kernel/os (i.e. Linux or > FreeBSD) pretty much the same way how a pc bios boots them I > somehow doubt it would `taint' the FreeBSD kernel. =A0(And the dom0 > kernel also doesn't need any patches, you only then run the Luvalley > version of qemu-kvm in the dom0's userland.) > > =A0HTH, > =A0 =A0 =A0 =A0Juergen >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=2Nn8xeKudxb2uSR=aLx0GW43gVPCdL-=hjP7z>