theoldwizard1 wrote:
joshuajim wrote:
Mac has been running windows in virtual for over 10 years. Yeah, Windows the “innovator” :B
The only need to run "virtual machines" on any OS is to make up for a major flaw in the design of the OS !
In Windows Server's case, it is the Registery. The Registry was "invented" as a repository for application setup "data" that the end user could not easily screw up. But it was invented in the context of Windows being a SINGLE USER computing environment. This does not work when you want to run multiple client/server (database) apps that serve totally different clients.
This problem was solved over 30 years ago, but there was no way around the Registry that would turn Windows into a true multi-user OS.
For that matter, a large percentage of "database" applications could be easily implement with index sequential access (ISAM) files. That technology is probably 50 years old, but "not invented by Microsoft" or anyone in the UN*X/Linux crowd so now it is lost technology. SIGH ! BTDTGTT !!!
:R
I think you are quite mixed up.
"Registry" has nothing to do with "application setup" nor does it have anything to do with "single user" use.
Think of the Registry being like a shopping list for the OPERATING SYSTEM to go through on boot up. It is nothing more than a list of information on what to load, where to find it and all the parameters to use.
The main reason for VMs is to allow multiple "Guest" operating systems to be setup on ONE SINGLE PC.
A VM (Virtual Machine), is in a nutshell a SIMULATED "PC" HARDWARE environment. This environment simulates a processor, memory, video cards, NIC cards, USB ports, hard drives, ect.
The advantages of a VM is all of this is contained in ONE SINGLE VM FILE on the HOST PC. So, in essence, you can create a VM, back it up by copying the VM file, restore that file if something goes sideways and be backup and running within minutes..
In addition, you CAN on the right Host hardware, DUPLICATE hundreds of VMs on ONE HOST PC provided you have licensing for that.
In business using VMs can REDUCE a server farm from thousands of "servers" down to a few servers with HUNDREDS of VMs.. Administration of the network now gets simpler and backup and restores get simpler and not to mention considerably less server space, less power used and less cost to operate and maintain.
VMs were never intended for the "Home user".
And yes, the OPs PC is very light on memory which is critical for hosting a VM.
Your Host PC hardware must have enough memory for the "Host" OS and then extra memory for each "Guest" OS (each VM).
It has been a while since I setup VMs but here is what I learned many years ago.
There are minimum memory requirements for the Host and Guest, OP might be able to skirt that a bit by specifying the absolute MIN memory when setting up the GUEST VM which at one time was about 2 GB of Ram on the Guest.. 2 GB of ram in the GUEST VM may not be enough for a 32 or 64 bit Win10 Guest but should be enough for something like 32 bit XP or Win7.
But in doing so, that will only leave 4 gig for the HOST when the GUEST VM is running.
When setting up a VM, you must also specify a "drive size", this will create the VM file to that size. If you have a 500 gb drive on your HOST you do not want to specify 500 GB, not enough space to do that.. In other words the GUEST VM can only read and write within the VM file so you will need to specify a drive space much smaller than the physical HD you have to work with..
Once setup, then you will have to create Virtual connections like Network and USB.. between the HOST AND GUEST.
There is less demanding GUEST VMs, a lot of gamers that like the old school DOS games often rely on VMs like DOSBOX to play their old games..
