![]() Strictly speaking I am not going to fret about win10 license 'validity' to the degree beyond this. I am slightly confused how such a process can be time intensive (a few config stanzas for pass through in the KVM VM Config file most likely? But maybe there is more song and dance?) If you can point me to any hints on how to do the SLIC Table pass through from physical to virtual, that would be great. ie, just plan on spending the extra $200 or whatever for a vanilla Win10pro license key for install purpose for the VM. I am curious if anyone knows, is there any way I can make use of this Bios-embedded license key for my windows VM Guest install on proxmox? Or is that more or less impossible, because we're using a virtualized bios for Proxmox KVM Win10 guest, and no way to harvest/pass through this "Windows license key" from the underlying hardware. The system hardware - comes out of box with a Win10Pro license bundled, which is 'burned into the bios' of the hardware / motherboard. With an add-in LSI Raid card it makes a decent little server (Pair of SSD drives for proxmox, and probably a pair of SATA drives for a 'bulk backup data mirror storage disk volume'). The Lenovo workstation I'm planning to use is a tower / i7 CPU / support for 32gb ram easily / decent solid system. They need 2 x small VMs, one will be a linux ClearOS "NAS Fileserver" and the second will be Win10Pro for running Sage Simply Accounting. I'm setting up a small 'lenovo mid-level workstation' as a small on-prem server for a client. ![]() Hi, a 'fun' question I wonder if anyone has experience with. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |