- verifiedPhysical vs virtual: What's your poison?
You apply a slice of your host’s resources to a visitor, allowing that guest to grip a fixed amount of RAM, share X few of cores and access other resources such as optical drives or network cards. You can prevent guests on or off at will as easily as mounting an .iso in Daemon Tools.
While this will untangle justify the basics of virtualization to the friendly of computer adept who already has Daemon Tools installed, explaining this to your pointy-haired boss is another defy entirely. I have gone through many divergent models of explanation and the one that has worked most artistically so far is a boat analogy.
Fancy a large ocean-effective vessel whose engines tool along a single large propeller. That one ample propeller has an awful lot of power readily obtainable to it, but the only way to steer is with a rudder placed behind it. It’s positively good at going in a unsmiling line, but remarkably ungainly and awkward for anything else.
Now think of more newfangled ships, where you instead use the generators to put electricity, and drive dozens or even hundreds of smaller propellers. As contrasted with of having rudders these smaller and more numerous propellers can opportunity in 360 degrees contribution the ability to individually without thrust. You lose a pocket-sized bit of efficiency in converting to electrical power and the accepted all over the ship to power your props, but now your deliver is far more easy to steer.