CONCEPT 1: Linux Installation Methods (Dual Boot, VM, Bare Metal)

Choosing how to install Linux is one of the most foundational decisions a system administrator, developer, or enthusiast will make. The installation method directly influences performance, isolation, hardware access, ease of experimentation, and long-term maintainability. The three primary approaches—bare metal, virtual machine (VM), and dual boot—each solve different problems and come with distinct trade-offs in architecture, workflow, and operational behavior.

This chapter explores each method in depth, from the underlying system architecture to practical implementation, real-world engineering considerations, and advanced usage patterns.

Understanding the Installation Landscape

At its core, installing Linux means placing a functional kernel, init system (most commonly systemd), root filesystem, and necessary userspace tools onto a storage medium that the bootloader can locate and execute.

The Linux kernel is a monolithic kernel that interacts directly with hardware through drivers compiled either statically or as loadable kernel modules. The bootloader (typically GRUB) is responsible for loading the kernel image (vmlinuz), initial ramdisk (initrd or initramfs), and passing kernel parameters.

Each installation method changes where and how this stack executes:

• Bare metal runs the kernel directly on physical CPU, memory, and devices.
• Virtual machine runs the kernel inside a hypervisor-managed environment.
• Dual boot shares physical hardware between two operating systems.

Bare Metal Installation: Maximum Performance and Direct Hardware Control

Bare metal installation means Linux runs natively on the physical hardware without any abstraction layer between the kernel and the CPU, memory, storage controllers, or peripherals.

Why Choose Bare Metal?

Bare metal delivers the highest possible performance because there is zero hypervisor overhead. All CPU cycles, memory bandwidth, and I/O operations go directly to your Linux environment. This approach is preferred for production servers, high-performance computing, gaming desktops, audio/video workstations, and any workload where latency or throughput is critical.

Hardware Preparation and UEFI vs BIOS

Modern systems use UEFI (Unified Extensible Firmware Interface) with GPT partitioning. Legacy systems may still use BIOS with MBR. During installation, you must decide on an EFI System Partition (ESP) formatted as FAT32 (typically 512 MiB) mounted at /boot/efi.

A recommended bare metal partition layout for a production system might look like this:

/dev/nvme0n1p1     512M     FAT32     /boot/efi     (ESP)
/dev/nvme0n1p2     1G       ext4      /boot
/dev/nvme0n1p3     remaining space    LVM physical volume

LVM (Logical Volume Manager) is strongly recommended because it allows online resizing of logical volumes without downtime.

Step-by-Step Bare Metal Installation Process

1. Create bootable media using dd, Rufus, or Ventoy.
2. Boot from the media and enter the live environment.
3. Partition disks using gdisk, fdisk, or the distribution installer.
4. Format partitions (mkfs.ext4, mkfs.fat, etc.).
5. Mount the target filesystem hierarchy under /mnt.
6. Use debootstrap, pacstrap, or the graphical installer to populate the root filesystem.
7. Generate fstab, chroot into the new system, install the bootloader, and configure networking.
8. Reboot and remove installation media.

Advanced Considerations

On bare metal, you have full control over kernel parameters passed via GRUB (quiet splash, mitigations=off, iommu=pt). You can compile a custom kernel tailored to your hardware, enable specific CPU features (AVX512, huge pages), and optimize I/O schedulers (mq-deadline, bfq, or none for NVMe).

Limitations: No easy rollback. Hardware failures affect the entire system. Testing new distributions requires physical hardware or reinstallation.

Virtual Machine Installation: Isolation, Flexibility, and Rapid Experimentation

Virtual machines run Linux inside a hypervisor such as KVM/QEMU, VirtualBox, VMware, or Hyper-V. The hypervisor presents virtualized hardware (vCPU, vRAM, virtio devices) to the guest.

Architecture of Modern Virtualization

KVM (Kernel-based Virtual Machine) turns the Linux kernel into a hypervisor by loading the kvm and kvm-intel/kvm-amd modules. QEMU provides device emulation, while virtio drivers deliver near-native performance for block, network, and graphics devices.

libvirt acts as a management layer, providing a unified API for creating, starting, and monitoring virtual machines.

Creating a High-Performance Linux VM

Here is a complete example using virt-install (recommended for production-grade VMs):

virt-install \
  --name ubuntu-server-24 \
  --ram 8192 \
  --vcpus 8 \
  --cpu host-passthrough \
  --disk path=/var/lib/libvirt/images/ubuntu24.qcow2,size=80,format=qcow2,bus=virtio \
  --network network=default,model=virtio \
  --graphics none \
  --console pty,target_type=serial \
  --location https://releases.ubuntu.com/24.04/ubuntu-24.04-live-server-amd64.iso \
  --extra-args 'console=ttyS0,115200n8'

Key options explained:

• --cpu host-passthrough: Exposes the full host CPU capabilities to the guest for maximum performance.
• virtio drivers: Paravirtualized devices that bypass much of the emulation overhead.
• qcow2 format: Supports snapshots, compression, and thin provisioning.

Advanced VM Techniques

• PCI passthrough: Assign physical GPUs, NICs, or storage controllers directly to the VM using VFIO.
• Nested virtualization: Run VMs inside VMs (useful for testing Kubernetes clusters).
• Live migration: Move running VMs between hosts with zero downtime.

Advantages: Snapshots, easy cloning, hardware independence, and the ability to run multiple distributions simultaneously.

Limitations: Slight performance overhead (typically 2-10% for CPU-bound tasks, higher for I/O without virtio). Resource contention on the host.

Dual Boot: Sharing Physical Hardware Between Operating Systems

Dual boot allows both Linux and another OS (usually Windows) to coexist on the same physical machine, with the bootloader presenting a choice at startup.

Bootloader Architecture in Dual Boot

GRUB is installed to the EFI System Partition and configured to detect other operating systems via os-prober. The chainloading mechanism works as follows:

1. UEFI firmware loads GRUB.efi.
2. GRUB reads its configuration (/boot/grub/grub.cfg).
3. Menu is displayed with entries for Linux and Windows.
4. Selecting Windows chainloads the Windows Boot Manager.

Safe Dual Boot Installation Strategy

Always install Windows first. Windows will claim the entire disk and create its own partitions (EFI, MSR, Windows, Recovery). Then:

1. Shrink the Windows partition from within Windows using Disk Management or diskpart.
2. Boot from Linux media.
3. Install Linux into the unallocated space.
4. Let the Linux installer install GRUB to the EFI partition (it will automatically detect Windows).
5. Update GRUB configuration: sudo update-grub.

Common Challenges and Solutions

• Fast Startup in Windows can leave NTFS partitions in an inconsistent state. Disable it.
• Time synchronization: Windows uses local time, Linux uses UTC. Set Linux to use local time or Windows to use UTC.
• Secure Boot: Sign your custom kernels or use distribution-provided signed bootloaders.
• Shared data partition: Create an NTFS or exFAT partition accessible by both systems.

Advantages: Native performance for both OSes, access to hardware-specific applications.

Limitations: Risk of bootloader corruption, difficulty in resizing partitions later, and inability to run both OSes simultaneously.

Choosing the Right Method: Decision Framework

Consider these factors when deciding:

• Performance needs: Bare metal for maximum speed, VM for acceptable performance with isolation.
• Experimentation frequency: VM wins for rapid testing.
• Hardware availability: Dual boot or bare metal when you have dedicated machines.
• Production requirements: Bare metal or Type-1 hypervisor (KVM) for servers.
• Development workflow: Many engineers maintain a bare metal workstation for daily work and multiple VMs for isolated testing environments.

Best practice: Start with a virtual machine to learn safely, move to dual boot for daily driver usage, and deploy to bare metal for production workloads.

Practical Engineering Workflows

Professional Linux users often combine methods. A common setup includes:

• Bare metal host running KVM + libvirt.
• Multiple specialized VMs (development, testing, CI/CD).
• Physical dual-boot machine for graphics-intensive work.
• Cloud instances for additional capacity.

This hybrid approach provides both performance and flexibility.