Add passing SLIC ACPI table to HVM guest to allow activate OEM Windows

[jevank]

Allow use SLIC ACPI table to activate OEM installed Windows
In order to use Windows OEM install media, the SLIC table must be passed to a
guest. In addition all the OEM table IDs must match the SLIC or Windows will
think it is invalid and the install ends up unactivated.

Describe the solution you'd like
Libxl support passing additional ACPI tables to HVM guest (acpi_firmware param), but it need also updating OEM ID it tables. It could possible with OpenXT patch.

Second problem is libvirl libxl driver have no support to use acpi_firmware setting while have supporting SLIC table defining in domain common schema.

Where is the value to a user, and who might that user be?
Any user with OEM Windows 7 could activate it

Additional context
All PR are ready to use

[jevank]

short HowTo:

1. Copy base xen template to create custom one
   cp /usr/share/qubes/templates/libvirt/xen.xml /etc/qubes/templates/libvirt/xen/by-name/win7.xml
2. In <os> section add
   <acpi>
<table type='slic'>/sys/firmware/acpi/tables/SLIC</table>
</acpi>

[marmarek]

Instead of copying the whole template, it should be enough to extend os block, like this:

{% extends "libvirt/xen.xml" %}
{% block os %}
{% super() %}
<acpi>
<table type='slic'>/sys/firmware/acpi/tables/SLIC</table>
</acpi>
{% endblock %}

As for the patches, have you considered sending them upstream (libvirt and xen respectively)?

[jevank]

ok, extending looks appropriate.

I think to offer libvirt patch to upstream, it is simple and useful. As for xen patch first I got in from OpenXT, second right now difficult to test upstream build for me. Perhaps patching to R4.1 packages will help with it.

[unman]

@jevank I'm intrigued, because I have activated Win7 on various machines without this patch without any problem.
Which manufacturer and Windows version gave you trouble?

Even if you couldn't register automatically, were you not able to activate by phone? I've had to do that in the past even with machines straight from the manufacturer.

[marmarek]

I don't think it's about inability to activate manually. It's rather about activating automatically with built-in OEM license (instead of of manually typing the key from the sticker).

[jevank]

@unman OEM SLP type of license

Computers that come pre-installed with Windows from large manufacturers usually come with two Product Keys.

OEM SLP: This is the key that came in Windows (from the factory). It works by connecting to a BIOS flag (the SLIC table) found only on computers from that Manufacturer. It also checks for the existence of proper matching licenses in the OS itself. Once it sees both, it self-activates every time the machine is rebooted.

COA SLP: This is the key seen on the sticker located on the side, bottom or in the battery compartment of your machine. This key is for use if the OEM SLP self-activation stops working for whatever reason.

You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment), using the Change Product Key link at the bottom of the System properties page.

You may need to activate by phone.

https://social.microsoft.com/Forums/en-US/6fb311e4-8498-4fdb-82ea-c29a3001dfca/windows-7-hp-oem-activation-from-clean-install

[jevank]

This type of activation could be offine completely