The virtual unit on which the system runs is completely customizable, and lets you change the virtual hardware according to your needs, be it the processor, RAM memory, or the storage space. You would then choose at boot time which disk to boot.VirtualBox is a multi platform and open-source virtualization tool for Windows, Linux, Mac OS X, and other operating systems, that lets you create virtual disc units in which you can install a guest operating system within the one you normally use on your computer, using it in the same way as if it was actually installed. You could even attach both disks to the same VM at the same time and dual boot as you would on a physical PC. This is like swapping disks in a real PC whereas using 2 VMs is like to separate PCs that you need separate licenses for.
The VM can run with either disk attached and it will be activated (although not at the same time obviously as it is impossible to simultaneously boot from 2 disks). vbox file you'll see the HardDisk uuid change but not the Machine uuid when you do this. The digital license is based on the Machine uuid you found in the. vbox which is the blue cube in your picture you should be able to open it in a text editor vbox it keeps as a backup in case something goes wrong and you want to revert. I found the following in this file "Windows 10 Version 1809 (32-bit).vbox-prev". I found the following in this file "Windows 10 Version 1809.vbox-prev".
You need to look for that type of string of numbers somewhere - note these are unique to each VM - your machine will generate a valid uuid for its mobo bios and os. Uuid.location = "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy" It's good to know this as you can also configure the VM with all sorts of extra options that don't appear in the standard "Virtual Machine" wizard or menu screens.ĮxtendedConfigFile = "CentOS 7 64-bit.vmxf"
It's a text file so you can open with notepad etc. In vmware it's in the config.vmx file : (ON THE HOST - not within the VM itself or the Virtual hard disks).
With VMware you get the prompt at first boot of a moved / copied VM so the case doesn't arise -howver there must be some uuidd / guuid info in some configuration file somewhere. I'm not a VBOX user - so I would address that question to VBOX users - however I can't see any problem with running a VM of a 32 bit windows system and a 64 bit windows system if it's in the same retail package - not sure why you would want to but people do all sorts of things with their systems so not for me to say other than unless you are running really onld legacy hardware there doesn't seem any point on running 32 bit windows any more.
0 kommentar(er)
