From mboxrd@z Thu Jan  1 00:00:00 1970
From: "firewatcher" <firewatcher@yeah.net>
Subject: virtualized boot loader
Date: Sat, 28 Jun 2008 22:30:50 +0800
Message-ID: <200806282230502031301@yeah.net>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Hi all,

When a box is powered on, first bios is loaded and executed, then the boot loader, then the operating system. 

Now with the introduction of VMM, the boot loader first loads the VMM, then loads the OS.

Why not implement a boot loader which is itself a VMM? That is, the boot loader can fulfil its traditional function, as to
select to load an OS separately, but also, it can function as a VMM, which can load two or more OSes as guest OSes simultaneously.

I have started a project with the name vGRUB, to enhance GRUB with the virtualization functions of XEN. The aim of the project is to
simplify the hierachy of software. That is, vGRUB is the firmware that between bios and OSes.

vGRUB equals GRUB plus XEN.

I am anxious for all your suggestions. Thanks a lot.

FireWatcher