You should not use this as legal advice since only qualified legal professionals can provide you with information relevant to your particular circumstances. I've simply provided my experience when dealing with these scenarios in a professional capacity, it may not be all inclusive but a best effort has been made for accuracy. Please note (IANAL Disclaimer): I'm not a lawyer, and licensing is a legal document. There may be additional steps needed to activate since OEM's provide hardware information to MS which would need to match what the OS can detect without an activation code from MS direct. The usual caveats being you cannot use remote desktop or the remote desktop protocol to connect to the VM without having a proper base license in place (Windows OS), and even then it can only be done for administrator purposes (not general use).Īdditionally, you cannot move the VM to another computer. Regarding licensing for W10 its not a problem so long as you follow the terms of the license. You may also need to install the Windows 10 from media, physical to vm backup/restores historically don't work well since there are some low level drivers that must be installed at OS deployment which are not normally included.
If you expect native performance you'll usually need to do a VFIO/OVMF pass-thru which requires two separate video adapters (usually integrated with a gpu), and some looking glass magick for best results. There are ways you can pass these tables through from the host with KVM I'm not aware of a way to do this with big-Os virtualbox.
Usually its located as binary in the MSDM acpi table which can be printed out as a hexdump with xxd. This is usually visible from /sys/firmware/acpi/tables. Windows 10 checks the BIOS/EFI tables for your license key information.
0 kommentar(er)
