Book Image

Mastering KVM Virtualization - Second Edition

By : Vedran Dakic, Humble Devassy Chirammal, Prasad Mukhedkar, Anil Vettathu
Book Image

Mastering KVM Virtualization - Second Edition

By: Vedran Dakic, Humble Devassy Chirammal, Prasad Mukhedkar, Anil Vettathu

Overview of this book

Kernel-based Virtual Machine (KVM) enables you to virtualize your data center by transforming your Linux operating system into a powerful hypervisor that allows you to manage multiple operating systems with minimal fuss. With this book, you'll gain insights into configuring, troubleshooting, and fixing bugs in KVM virtualization and related software. This second edition of Mastering KVM Virtualization is updated to cover the latest developments in the core KVM components - libvirt and QEMU. Starting with the basics of Linux virtualization, you'll explore VM lifecycle management and migration techniques. You’ll then learn how to use SPICE and VNC protocols while creating VMs and discover best practices for using snapshots. As you progress, you'll integrate third-party tools with Ansible for automation and orchestration. You’ll also learn to scale out and monitor your environments, and will cover oVirt, OpenStack, Eucalyptus, AWS, and ELK stack. Throughout the book, you’ll find out more about tools such as Cloud-Init and Cloudbase-Init. Finally, you'll be taken through the performance tuning and troubleshooting guidelines for KVM-based virtual machines and a hypervisor. By the end of this book, you'll be well-versed with KVM virtualization and the tools and technologies needed to build and manage diverse virtualization environments.
Table of Contents (22 chapters)
Section 1: KVM Virtualization Basics
Section 2: libvirt and ovirt for Virtual Machine Management
Section 3: Automation, Customization, and Orchestration for KVM VMs
Section 4: Scalability, Monitoring, Performance Tuning, and Troubleshooting

Best practices for troubleshooting KVM issues

There are some common-sense best practices when approaching troubleshooting KVM issues. Let's list some of them:

  • Keep it simple, in configuration: What good does a situation in which you deployed 50 OpenStack hosts across three subnets in one site do? Just because you can subnet to an inch of an IP range's life doesn't mean you should. Just because you have eight available connections on your server doesn't mean that you should LACP all of them to access iSCSI storage. Think about end-to-end configuration (for example, Jumbo Frames configuration for iSCSI networks). Simple configuration almost always means simpler troubleshooting.
  • Keep it simple, in troubleshooting: Don't go chasing the super-complex scenarios first. Start simple. Start with log files. Check what's written there. With time, use your gut feeling as it will develop and you'll be able to trust it.
  • Use monitoring tools such...