Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By : Roman Levchenko, EDVALDO ALESSANDRO CARDOSO
Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By: Roman Levchenko, EDVALDO ALESSANDRO CARDOSO

Overview of this book

Virtual Machine Manager (VMM) 2016 is part of the System Center suite to configure and manage datacenters and offers a unified management experience on-premises and Azure cloud. This book will be your best companion for day-to-day virtualization needs within your organization, as it takes you through a series of recipes to simplify and plan a highly scalable and available virtual infrastructure. You will learn the deployment tips, techniques, and solutions designed to show users how to improve VMM 2016 in a real-world scenario. The chapters are divided in a way that will allow you to implement the VMM 2016 and additional solutions required to effectively manage and monitor your fabrics and clouds. We will cover the most important new features in VMM 2016 across networking, storage, and compute, including brand new Guarded Fabric, Shielded VMs and Storage Spaces Direct. The recipes in the book provide step-by-step instructions giving you the simplest way to dive into VMM fabric concepts, private cloud, and integration with external solutions such as VMware, Operations Manager, and the Windows Azure Pack. By the end of this book, you will be armed with the knowledge you require to start designing and implementing virtual infrastructures in VMM 2016.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Configuring availability options and virtual NUMA for VMs


Since VMM 2012 SP1, you can configure availability options for VMs that are deployed on Hyper-V host clusters, which include:

  • VM priority: By configuring these settings, the host clusters will be instructed to start orp place high-priority VMs before medium- or low-priority VMs, ensuring that (for better performance) the high-priority VMs are allocated memory and other resources first.
  • Preferred and possible owners of VMs: These settings influence the placement of VMs on the host cluster nodes. By default, there is no preferred owner, which means that the possible owners include all cluster nodes.
  • Availability sets: By placing VMs in an availability set (to improve continuity of service), VMM will attempt to keep those VMs on separate hosts whenever possible.

You can also configure NUMA, which is a memory architecture that is used in multiprocessor systems. NUMA tries to reduce the gap between the speed of the CPU and the memory usage...