How hypervisors create virtual machines, allocate host resources, and support isolated testing and training environments.
A hypervisor creates and runs virtual machines (VMs), each with a virtual CPU, memory, storage, and network configuration backed by physical host resources.
| Hypervisor type | Runs on | Typical use |
|---|---|---|
| Type 1 | Directly on server hardware | Centralized infrastructure workloads |
| Type 2 | On a host operating system | Local development, training, testing, and desktop labs |
Guest memory, virtual disks, and virtual CPUs consume host resources. A VM can be slow because the host lacks available RAM, storage capacity, CPU time, or network access; increasing guest settings without checking the host can worsen the problem.
A snapshot records a VM state to make short-term rollback convenient. It is not a replacement for backups: it may depend on the same storage as the VM and does not independently protect against host failure, deletion, or a broader incident.
Use a local VM to test a new utility or configuration before applying it to an everyday workstation. The VM isolates the test and makes rollback easier, while important test data still requires an ordinary backup.