Virtual Machine
Virtual Machine
A software-defined computer with virtual CPU, memory, disks and network adapters.
In everyday business: A company can run a domain controller, file server and Linux application as separate servers on one host.
MODERN SERVERS
How Modern Servers and Virtual Hosts Work
Understand bare metal, hypervisors, virtual machines, storage and network abstraction before configuring a production host.
Book 3 | Chapter 1
Chapter opening
Chapter 1 moves from the course overview into how modern servers and virtual hosts work. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider servers and virtualization technical textbook, what normal operation looks like, and how to prove the result in the field.
This is the first chapter in the sequence, so it establishes concepts that later chapters build on.
Learning objectives
- Explain the main purpose of How Modern Servers and Virtual Hosts Work in plain language.
- Trace CPU, memory, network and storage from a VM through the hypervisor to physical hardware.
- Use evidence to separate a design problem from a configuration or physical fault.
- Describe the business impact of a failure and the evidence required for handover.
Why this matters in a real company
Virtualization lets a company run several independent server workloads on fewer physical machines. The benefit is flexibility and easier recovery, but one badly designed host can also become a large single point of failure.
PLAIN ENGLISH
Technical terms used in this chapter
You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.
Virtual Host
Web Virtual Host
A web-server configuration that lets one server host multiple websites using different names or addresses.
In everyday business: One server can host several business websites separately.
Hypervisor
Hypervisor
Software that lets one physical server run multiple isolated virtual machines.
In everyday business: One powerful server can safely run several separate business servers.
Snapshot
Snapshot
A point-in-time storage or VM state used for short-term rollback depending on the platform.
In everyday business: It can quickly undo a bad change, but it is not automatically an independent backup.
Latency
Latency
The delay before an operation or packet completes.
In everyday business: Users experience high latency as slowness even when headline bandwidth looks good.
Volume
Container Volume
Persistent storage kept separately from the short-lived container filesystem.
In everyday business: Company data can survive when an application container is replaced.
Backup
Backup
An independent recoverable copy of data or system state.
In everyday business: It is the safety net for deletion, corruption, ransomware, hardware loss or major mistakes.
vCPU
Virtual CPU
A virtual processor assigned to a VM and scheduled onto the host's physical CPU resources.
In everyday business: It is how a VM gets computing time without owning a physical processor.
BUSINESS TRANSLATION
What this means outside the server room
This topic affects the systems staff depend on for sign-in, files, applications and business continuity. The technical design determines how easy the environment is to manage and how painful a failure becomes.
VLAN
What it means: A VLAN creates a separate logical network even when devices share the same physical switches.
In normal business language: Think of one office building with separate departments using the same corridors but different access-controlled areas. Staff, cameras, voice and guests can share the same switching hardware without all being in one open network.
Why the decision matters: Use VLANs to separate traffic for security, performance and easier troubleshooting without buying a separate physical switch for every department.
Hypervisor
What it means: A hypervisor lets one physical server run several isolated virtual machines.
In normal business language: Think of one office building divided into secure independent suites. The building is shared, but each tenant operates separately.
Why the decision matters: Virtualization reduces hardware sprawl and improves flexibility, but the physical host becomes important because several business systems can depend on it.
Virtual Machine
What it means: A virtual machine is a software-defined computer with its own operating system, memory, CPU allocation, disks and network interfaces.
In normal business language: It behaves like a separate server even though several VMs may share one physical machine.
Why the decision matters: VMs are useful for separating roles such as domain control, file sharing and applications while keeping management and recovery flexible.
Backup
What it means: A backup is an independent recoverable copy of data or system state.
In normal business language: Think of it as having a duplicate of important company records stored safely away from the live filing cabinet.
Why the decision matters: A backup only counts if it can be restored. Test recovery, not just backup completion.
Snapshot
What it means: A snapshot is a point-in-time state of a storage volume or VM on the same platform.
In normal business language: It is like a quick undo point inside the same office. Very useful for rolling back a mistake, but not enough if the whole storage system is lost.
Why the decision matters: Use snapshots for fast rollback, but keep independent backups for real disaster recovery.
Firewall
What it means: A firewall controls which network connections are allowed between users, systems and external networks.
In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.
Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.
Chapter contents
1.1 Terminology first
In infrastructure, a virtualisation host is the physical server that runs a hypervisor and hosts virtual machines. In web-server terminology, virtual host can also mean multiple websites served by one web server. This guide is about virtualisation hosts.
Why virtualise
Instead of dedicating one physical server to one workload, a hypervisor partitions CPU, memory, network and storage resources among multiple VMs. Each VM has its own guest operating system and applications.
What the hypervisor controls
- vCPU scheduling onto physical cores.
- Guest memory mapping.
- Virtual NICs and virtual switching.
- Virtual disks backed by files, logical volumes or shared storage.
- VM lifecycle, snapshots/checkpoints and migration features.
What can be virtualised
Domain controllers, file servers, application servers, Linux services, monitoring systems and management servers are commonly virtualised. Hardware-dependent or extremely latency-sensitive applications can have special requirements.
What virtualisation does not solve
- One host is still one hardware failure domain.
- A snapshot is not an independent backup.
- CPU/RAM overcommit can make many VMs slow at once.
- One failed storage pool can affect many VMs simultaneously.
Client benefit
A properly designed platform uses hardware efficiently and makes workloads easier to isolate, recover, migrate and expand.
DEEPER TEACHING
Virtualization from resource allocation to failure domains
Virtualization separates the operating system from the physical server. Instead of an application "owning" a physical motherboard, CPU and disks, the VM sees virtual hardware presented by the hypervisor.
vCPU is scheduled time, not a dedicated processor
A VM with four vCPUs does not necessarily own four physical CPU cores. The hypervisor schedules virtual processors onto available physical execution resources. Allocating more vCPU than a workload can use may increase scheduling complexity without making the application faster.
Memory planning
Start with the guest operating system and application requirement, then add the host's own memory needs and headroom. A host with 128 GB RAM cannot safely allocate every byte to guests. Management services, hypervisor overhead, failover requirements and growth need capacity too.
Storage path matters
A virtual disk might be a VHDX, qcow2, VMDK or logical volume, but the VM's performance ultimately depends on physical media or network storage underneath. Ten fast-looking virtual disks can still share one overloaded physical RAID set.
Worked host-capacity example
Suppose a server has 128 GB RAM. The planned VMs require 16 GB, 24 GB, 12 GB, 8 GB and 32 GB. Their planned total is 92 GB.
Total physical RAM 128 GB
Planned VM allocation 92 GB
Remaining before host use 36 GB
That remaining 36 GB is not automatically "free for another 36 GB VM". Reserve memory for the host, monitoring, peak behaviour and future growth. The correct reserve depends on platform and workload.
Virtual networking walkthrough
- The VM sends an Ethernet frame through its virtual NIC.
- The hypervisor's virtual switch decides where to forward it.
- If the destination is external, traffic leaves through a physical NIC or team/bond.
- The physical switch must carry the correct VLAN.
- The return path must reach the same VM network.
A VM that cannot reach the LAN can therefore fail at the guest IP layer, guest firewall, vNIC, virtual switch, VLAN tagging, host uplink or physical switch.
Checkpoints vs backups
Microsoft documents Hyper-V checkpoints as a way to capture a VM state and revert changes. Standard checkpoints can include VM memory state; production checkpoints use guest-aware mechanisms such as VSS or filesystem freeze. Microsoft also cautions that checkpoints are not a complete backup strategy. Treat them as short-term change-control tools unless your backup product intentionally uses them as part of a supported process.
WORKED BUSINESS SCENARIO
Scenario: five business servers now run on one host
The company consolidates a domain controller, file server, application server, monitoring server and Linux service onto one virtualization host.
What the chapter teaches us: Hardware use is improved, but one host, one storage pool or one network uplink can now affect several services at once. Virtualization changes the failure domain rather than removing it.
Think it through
- Which physical components can now stop all five services?
- What must be backed up independently?
- How would you prove that network and storage paths are resilient?
PRACTICAL WORK
Hands-on lab
Create one small lab VM, connect it to the intended virtual network, install an OS, record its vCPU, RAM and disk allocation, and prove network and storage paths.
Troubleshooting exercise
A VM is running but cannot reach the LAN. Check guest IP, guest firewall, vNIC, virtual switch or bridge, VLAN, host uplink and physical switch in that sequence.
Chapter field checklist
- I can explain the subject without relying only on acronyms.
- I can draw or describe the main traffic, storage, power or service path.
- I know what normal operation should look like.
- I know which logs, counters or test results prove the result.
- I can explain the business impact if this component fails.
- I would document the final configuration and evidence at handover.
Chapter summary
How Modern Servers and Virtual Hosts Work should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.
END OF CHAPTER
Review questions
- Explain the subject in plain language to a business owner.
- List the main dependencies that must be healthy before this service can work.
- Describe one realistic failure and the first three pieces of evidence you would collect.
- Explain what should be documented at handover.
- Which physical failures can affect multiple VMs at once?
- Why is a VM checkpoint not automatically a backup?
A good answer should explain the reason, not only repeat a product name or command.