Can I run virtual windows with my OEM license?
Solution 1:
Like other answers have mentioned, it is allowed by the license as long as you only use one instance.
As to how to do it in practice, you need to copy the ACPI tables to the virtual machine. The relevant tables are, depending on how new your machine is, MSDM
and SLIC
. You can copy them as follows:
ls /sys/firmware/acpi/tables/
to see what tables your system has. Older systems have onlyMSDM
, newer ones have both.Copy the tables to a single file:
sudo cat /sys/firmware/acpi/tables/MSDM /sys/firmware/acpi/tables/SLIC > custom_acpi
Set a VirtualBox attribute on the machine:
VBoxManage setextradata "Windows 10" "VBoxInternal/Devices/acpi/0/Config/CustomTable" /home/..../custom_acpi
where the last argument is the full path tocustom_acpi
file created in previous step.You can see the product key with
strings custom_acpi
, but Windows 10 may refuse it as it is an OEM key. However if you continue the installation (select "I'm reinstalling Windows"), it will automatically activate after the installation is complete.
Solution 2:
- Backup your Windows installation.
- Uninstall Windows from your hard drive.
- Install Windows in a VM.
- Ensure the Windows installation has internet access.
- Attempt to activate the installation. You may need to call Microsoft to complete this step over the phone.
If they ask you why your are re-activating, tell them you have removed the old installation and changed your system configuration and that you are now reinstalling. (All true.)
Don't volunteer that the Windows 7 key is OEM. Your Windows 10 entitlement may or may not be marked as originating from OEM. If they say that it is OEM and that you cannot use it to activate, then you know. Say thanks and end the call. Restore your backup from step 1 and stick with dual boot, or purchase a copy of Windows 10 and activate yours that way.
Of course, you could always install Hyper-V component of Windows 10 and run your Linux inside. No licensing issues that way. And it may be installed and running by default.
Also, before step 2, you might try to find some sort of P2V solution. This basically takes an 'image' of your physical system and converts it to a virtual machine. VirtualBox wiki article. This may trigger a reactivation due to the significant change in the HAL (hardware abstraction layer).