This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Using LinuxBIOS as virtual firmware

To: "Lu, Yinghai" <yinghai.lu@xxxxxxx>, "John Levon" <levon@xxxxxxxxxxxxxxxxx>, rminnich@xxxxxxxx, "Stefan Reinauer" <stepan@xxxxxxxxxxxx>
Subject: [Xen-devel] Using LinuxBIOS as virtual firmware
From: "Lu, Yinghai" <yinghai.lu@xxxxxxx>
Date: Fri, 14 Jul 2006 17:40:48 -0700
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Michael Loehr <MLOEHR@xxxxxxxxxx>
Delivery-date: Fri, 14 Jul 2006 17:41:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcanUdyY8FYF6oO/SwSq/TF5rI84zgAEFXPgABCLjqA=
Thread-topic: Using LinuxBIOS as virtual firmware
OK, I did some tests on xen and LinuxBIOS.

I built special LinuxBIOS, and using ADLO as payload. (ADLO will have
bochs bios in it).
With that I could boot Linux and windows with vcpu=1, and no acpi, and

The real LinuxBIOS can create acpi tables and mptable and pirq table
dynamically. So if some cpus are not installed, these tables may be

So Next I could modify the ioemu to make it more AMD like. And device
model will be amd64+amd8111. and the device model will only set
read_only pci conf. and let the LinuxBIOS to enumerate the PCI bus and
allocate the source. Also LinuxBIOS could create the acpi tables etc
according to the pci conf and msr reading. Then the driver model could
be some tide, and don't need to do init thing for firmeare.

The good is the LinuxBIOS for amd64 platform is there already, and the
almost 99.9% LinuxBIOS is in C. we only use bochs for BIOS call. Also it
could be get more cleaned.

The drawback is that to keep consistent with qemu, I may need to update
qemu to support amd64 model. So we can share the Diskimage between Qemu
and xen.
I tried the winxp installed image with qemu and I got blue screen. I
need reinstall that in xen with LinuxBIOS.

Is it a good way?

Any comment?


Yinghai Lu

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lu, Yinghai
Sent: Friday, July 14, 2006 9:41 AM
To: John Levon; yhlu; rminnich@xxxxxxxx
Cc: Ian Pratt; Anthony Liguori; xen-devel@xxxxxxxxxxxxxxxxxxx; Mark
Williamson; Michael Loehr
Subject: RE: Xen bootloader (was: Re: [Xen-devel] Xen Roadmap proposal)

You need to make sure the format can be handle by kexec. It could handle
elf, linux kernel, grub.exe (for multiboot?), ...

Maybe it is off topic.
I am considering to use LinuxBIOS in hvmloader...then it could only
support Linux ( with etherboot and FILO can load kernel from network or
HD then kexec ). I can reuse LinuxBIOS ACPI code ...

If the guest OS need BIOS call, we may need to use ADLO and BOCHS to
feed the OS....----for windows and BSDs...


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>