On Tue, Mar 08, 2011 at 09:00:05AM -0800, Jordan Justen wrote:
On Mon, Mar 7, 2011 at 23:18, Stefan Hajnoczi stefanha@gmail.com wrote:
On Tue, Mar 8, 2011 at 12:54 AM, Jordan Justen jljusten@gmail.com wrote:
The biggest issue that you guys care about for OVMF is a lack of legacy bios compatibility (CSM). There has been no progress in this area. (However, it has now been suggested by someone on our dev list for a potential Google Summer of Code project. We will have to see if anything comes of this...)
That would be cool. Is there a way to just embed SeaBIOS? Or do the UEFI APIs still need to be around when CSM kicks in?
Yes, the UEFI system is still in place. The UEFI part still handles the majority of platform init, and calls into the CSM at various points. The CSM returns back to UEFI for all CSM calls, except the legacy boot.
Is there a concise list of these various callbacks between UEFI and CSM?
If SeaBIOS just needs to be loaded up for legacy boots, that doesn't sound too difficult. However, if SeaBIOS would need to translate various BIOS calls into UEFI calls - that sounds like it could be complex.
-Kevin
On Tue, Mar 8, 2011 at 18:23, Kevin O'Connor kevin@koconnor.net wrote:
On Tue, Mar 08, 2011 at 09:00:05AM -0800, Jordan Justen wrote:
Yes, the UEFI system is still in place. The UEFI part still handles the majority of platform init, and calls into the CSM at various points. The CSM returns back to UEFI for all CSM calls, except the legacy boot.
Is there a concise list of these various callbacks between UEFI and CSM?
If SeaBIOS just needs to be loaded up for legacy boots, that doesn't sound too difficult. However, if SeaBIOS would need to translate various BIOS calls into UEFI calls - that sounds like it could be complex.
A CSM does not really know about UEFI for the most part. Rather it carries out some tasks when request by the UEFI environment. The UEFI side still manages the high level boot flow (even for legacy boots). The CSM does not call into UEFI services, but just returns back to whoever invoked the CSM call.
The 16-bit CSM component interface is described in this file: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/IntelFrameworkPkg/I...
The full CSM specification document is available here: http://www.intel.com/technology/framework/spec.htm
Thanks,
-Jordan
Hi all,
This may come late in the discussion, but, has OVMF been tested with Mac OS X?
A decent Intel Macintosh emulation requires of course EFI + HFS.
Regards, Natalia Portillo
El 09/03/2011, a las 05:34, Jordan Justen escribió:
On Tue, Mar 8, 2011 at 18:23, Kevin O'Connor kevin@koconnor.net wrote:
On Tue, Mar 08, 2011 at 09:00:05AM -0800, Jordan Justen wrote:
Yes, the UEFI system is still in place. The UEFI part still handles the majority of platform init, and calls into the CSM at various points. The CSM returns back to UEFI for all CSM calls, except the legacy boot.
Is there a concise list of these various callbacks between UEFI and CSM?
If SeaBIOS just needs to be loaded up for legacy boots, that doesn't sound too difficult. However, if SeaBIOS would need to translate various BIOS calls into UEFI calls - that sounds like it could be complex.
A CSM does not really know about UEFI for the most part. Rather it carries out some tasks when request by the UEFI environment. The UEFI side still manages the high level boot flow (even for legacy boots). The CSM does not call into UEFI services, but just returns back to whoever invoked the CSM call.
The 16-bit CSM component interface is described in this file: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/IntelFrameworkPkg/I...
The full CSM specification document is available here: http://www.intel.com/technology/framework/spec.htm
Thanks,
-Jordan
On Wed, Mar 9, 2011 at 05:43, Natalia Portillo claunia@claunia.com wrote:
This may come late in the discussion, but, has OVMF been tested with Mac OS X?
No.
I don't think Apple considers VMs an acceptable usage environment for OS X. Please correct me if I am mistaken.
Thanks,
-Jordan
Hi, El 09/03/2011, a las 18:44, Jordan Justen escribió:
On Wed, Mar 9, 2011 at 05:43, Natalia Portillo claunia@claunia.com wrote:
This may come late in the discussion, but, has OVMF been tested with Mac OS X?
No.
I don't think Apple considers VMs an acceptable usage environment for OS X. Please correct me if I am mistaken.
Their EULA explicitly says that OS X Server can be run in VMs, as long as the VM is running on Apple hardware (VMWare Fusion, Parallels Desktop and VMWare ESXi for Mac are clearly authorized). For OS X non-server it just says "must run on Apple hardware" nothing specific as on VM, but none of the previously named took the risk.
VirtualBox is almost able to run OS X now but with some tricks and no "officially supported" statement.
As currently OS X searches for an encryption key on the hardware, and there has been code for providing it if being known in QEMU, as long as the requirement is reading that code on runtime on the real hardware, there should be no legal problems. MacOnLinux allowed to virtualize OS X on PowerPC and never received communications from Apple, even if it allowed to run on non-Apple PowerPC machines. PearPC emulated enough of a PowerMac to make OS X run and also never received communications from Apple.
In any case, IMHO, it's up to the user to respect or violate the EULA, we just provide the knife, it's not our fault it's used for assassination and not for cutting food.
Thanks,
-Jordan
-
Jordan Justen -
Kevin O'Connor -
Natalia Portillo