So do the activation only, after you have installed the guest additions to reduce the potential problem. Consequently the installation of the guest addition can also lead to the need to re-activate the Windows license. The guest additions act like a driver package, to give the guest OS the full access to the virtual hardware, which gets provided by VB. This means, that you only create additional trouble for you with your idea.Īdditional hint: Do the activation of Windows only after you have installed the guest additions, which has to be done from inside the VM. A number of hardware changes are allowed, but after having reached this limited you are forced to redo the activation.
The activation key gets computed by Windows dependent of the installed and recognized hardware (virtual hardware in this case). because of the activation mechanism of Windows. This allows users to set up virtual machines on a single physical device and use them simultaneously with a real machine. because this will hardly be noticeable as a benefit.Ģ. VMware Workstation is a perfect virtual machine tool that runs on 圆4 versions of Windows, macOS, and Linux. Giving more memory during installation and reducing it afterwards is a bad idea:ġ. As a rule of thumb: Don't give the VM more than 50 % of the available memory if you have 4 GB or more, 2 GB are really enough. On the other hand: The amount of RAM, which you assign to the VM gets lost for the host. I was thinking about allocating a lot of memory during installation, and then reduce it later on.Ī VM with too little memory will be slow, just as a physical installation on a computer with only low RAM will be slow. Will that affect the installation speed ? Hackerman1 wrote:does it matter how much memory i allocate during installation of the O/S (in the VM) ?