Features/ACPITableGeneration: Difference between revisions

From QEMU
(add feature page re acpi table generation)
 
Line 20: Line 20:


* When started with -M 1.6, QEMU generates all ACPI tables and passes them to the BIOS
* When started with -M 1.6, QEMU generates all ACPI tables and passes them to the BIOS
* When started with -M 1.5 and earlier, QEMU does not expose ACPI tables to BIOS
* When started with -M 1.5 and earlier, QEMU does not expose ACPI tables to BIOS (compatiblity mode)
  (compatiblity mode)
* BIOS includes generic code to load ACPI tables from QEMU and pass them to guest
* BIOS includes generic code to load ACPI tables from QEMU and pass them to guest



Revision as of 14:05, 14 July 2013

Summary

Generation of ACPI tables for guest BIOS in the hypervisor

Owner

Roadmap

Once implemented, QEMU will be able to extend information passed to Guest OS through ACPI tables without need for bios code changes. This is widely desired as a way to avoid the churn and proliferation of QEMU-specific interfaces associated with ACPI tables in bios code.

After QEMU 1.6

  • When started with -M 1.6, QEMU generates all ACPI tables and passes them to the BIOS
  • When started with -M 1.5 and earlier, QEMU does not expose ACPI tables to BIOS (compatiblity mode)
  • BIOS includes generic code to load ACPI tables from QEMU and pass them to guest

Status

Patchset implementing this functionality has been posted. seabios patchset seems acceptable - all comments have been addressed. Addressing review comments on the QEMU patchset.

Future plans

It might (or might not) be interesting to use a similar mechanism to pass in other tables, not just ACPI. This is TBD.