| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="changeacpicust">
|
|---|
| 4 | <title>Configuring Custom ACPI Tables</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>You can configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to present up to four custom ACPI tables
|
|---|
| 8 | to the guest. Use a command such as the following to configure custom ACPI tables. Note that
|
|---|
| 9 | <codeph>CustomTable1</codeph>, <codeph>CustomTable2</codeph>, and <codeph>CustomTable3</codeph> are available in
|
|---|
| 10 | addition to <codeph>CustomTable0</codeph>. </p>
|
|---|
| 11 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> \
|
|---|
| 12 | "VBoxInternal/Devices/acpi/0/Config/CustomTable0" "/<varname>path-to-table</varname>.bin"</pre>
|
|---|
| 13 | <p>Configuring custom ACPI tables can for example avoid the need for asking for a new product key on Windows Vista,
|
|---|
| 14 | Windows 7, Windows 8 and later guests. On Linux hosts, one of the system's ACPI tables can be read from
|
|---|
| 15 | <filepath>/sys/firmware/acpi/tables/</filepath>. </p>
|
|---|
| 16 | </body>
|
|---|
| 17 |
|
|---|
| 18 | </topic>
|
|---|
