102.6 Linux as a virtualization guest

Introduction

This lesson is mostly conceptual.

The main question is:

What changes when Linux runs inside a virtual machine, cloud instance, or container instead of on bare metal?

What you should be able to do after this lesson:

• Explain the difference between a virtual machine and a container.
• Recognize common cloud and virtualization terms.
• Understand what must change when a system is cloned from a template.
• Know why guest drivers and cloud-init matter.

Virtual Machine vs Container

Virtual machine

A VM emulates or presents virtual hardware to a guest OS. The guest runs its own kernel.

Linux container

A container shares the host kernel but isolates processes, filesystems, and networking.

Application container

This is usually a smaller container focused on one app or service.

Simple memory trick:

VM = own guest kernel; container = shared host kernel

Common IaaS Building Blocks

In cloud environments, you often see:

• compute instance
• block storage
• virtual networking
• images or templates

Linux inside a cloud guest still needs the basics:

• boot
• storage
• network
• identity

Why Cloned Systems Need Cleanup

If you clone a Linux machine and boot the copy as a new guest, some data should not stay duplicated.

Important examples:

• SSH host keys
• machine identity such as D-Bus machine id
• hostname or cloud metadata-based identity

If these stay duplicated, the clone may not behave like a truly new machine.

In plain words:

• a template should be reusable
• a deployed guest should still become its own machine

Guest Drivers

Many virtualization platforms provide guest drivers or guest integration tools.

Why they matter:

• better disk performance
• better network performance
• time sync
• cleaner shutdown or reboot behavior
• better display or clipboard integration on desktop hypervisors

Examples you may hear about:

• virtio
• VirtualBox guest additions
• VMware guest tools
• Hyper-V drivers

Images and Templates

Clouds and virtualization platforms often create systems from images.

The main idea:

• one prepared image can be reused many times
• each deployed guest should then get its own identity and settings

cloud-init

LPIC expects awareness of cloud-init.

In simple words:

• it is a first-boot initialization system often used in clouds
• it can set hostname, users, SSH keys, network config, and more

You do not need deep cloud-init internals here. Just know why it exists.

Images, Templates, and First Boot

When a cloud or virtualization platform creates a new guest, it often does not start from "nothing". It starts from an image or template.

That means there are two stages to think about:

1. the prepared image
2. the first boot customization

cloud-init often owns that second stage.

Helpful Guest-Side Checks

Some commands you may see:

systemd-detect-virt
lsmod | grep -E 'virtio|vbox|vmwgfx|hv_'
cloud-init status

These are awareness-level checks, not a full objective by themselves.

Example output from systemd-detect-virt:

container-other

What this shows:

• the current session is running in a container-like environment
• the exact value depends on the platform, but the command helps detect virtualization context

A Safe Cloning Checklist

When turning a Linux system into a reusable template:

1. Remove or regenerate SSH host keys as appropriate for the workflow.
2. Reset machine-specific identity if needed.
3. Make sure network config will not collide.
4. Confirm guest drivers are present.
5. Confirm first-boot tooling such as cloud-init behaves as expected.

Practice Step by Step

1) Explain VM vs container in one sentence each

1. VM: separate guest kernel on virtual hardware.
2. Container: isolated environment sharing the host kernel.

2) Think through cloning risk

1. A template is copied three times.
2. If all copies keep the same SSH host keys or machine id, identity problems can happen.
3. So a good template workflow resets machine-specific data.

Cheat Sheet

• virtual machine = guest with its own kernel
• Linux container = isolated environment sharing the host kernel
• application container = container focused on one app
• guest drivers improve integration and performance
• images and templates are reused deployment sources
• cloned guests should not keep duplicate host identity data
• cloud-init = first-boot cloud initialization tool