Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Windows Server 2016 Hyper-V Cookbook - Second Edition

You're reading from  Windows Server 2016 Hyper-V Cookbook - Second Edition

Product type Book
Published in Jan 2017
Publisher Packt
ISBN-13 9781785884313
Pages 524 pages
Edition 2nd Edition
Languages
Concepts
Authors (3):
Charbel Nemnom Charbel Nemnom
Profile icon Charbel Nemnom
Patrick Lownds Patrick Lownds
Profile icon Patrick Lownds
Leandro Carvalho Leandro Carvalho
Profile icon Leandro Carvalho
View More author details
Toc

Table of Contents (19) Chapters close

Windows Server 2016 Hyper-V Cookbook - Second Edition
Credits
About the Authors
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface
1. Installing and Managing Hyper-V in Full, Server Core, and Nano Server 2. Migrating and Upgrading Physical and Virtual Servers 3. Managing Disk and Network Settings 4. Saving Time and Cost with Hyper-V Automation 5. Hyper-V Best Practices, Tips, and Tricks 6. Security and Delegation of Control 7. Configuring High Availability in Hyper-V 8. Disaster Recovery for Hyper-V 9. Azure Site Recovery and Azure Backup for Hyper-V 10. Monitoring, Tuning, and Troubleshooting Hyper-V Hyper-V Architecture and Components Index

Optimizing virtual machines' resources


Sometimes, it is hard to know how much memory and CPU a VM needs. Even when capacity planning is performed, the VM will never use the full memory and CPU specification, resulting in poor memory utilization and a loss of CPU resources.

Windows Server 2008 R2 SP1 introduced a new feature, called Dynamic Memory (DM), which allows the memory on the host server to be shared with the VMs using a method called Ballooning. Ballooning ensures that the VMs use only the memory that they need, and releases it back to the host if another VM requires more memory. This allows the memory in the parent partition to be reallocated automatically through the VMs, increasing or decreasing it based on the current workload.

Let's use an example of a VM that was installed and configured to use 16 GB of memory. That is the value that you got from the planning phase. The problem is that the VM will only use 16 GB when a huge workload is created. This stipulation represents less...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}