Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering KVM Virtualization

You're reading from   Mastering KVM Virtualization Dive in to the cutting edge techniques of Linux KVM virtualization, and build the virtualization solutions your datacentre demands

Arrow left icon
Product type Paperback
Published in Aug 2016
Publisher Packt
ISBN-13 9781784399054
Length 468 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (22) Chapters Close

Mastering KVM Virtualization
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Understanding Linux Virtualization FREE CHAPTER 2. KVM Internals 3. Setting Up Standalone KVM Virtualization 4. Getting Started with libvirt and Creating Your First Virtual Machines 5. Network and Storage 6. Virtual Machine Lifecycle Management 7. Templates and Snapshots 8. Kimchi – An HTML5-Based Management Tool for KVM/libvirt 9. Software-Defined Networking for KVM Virtualization 10. Installing and Configuring the Virtual Datacenter Using oVirt 11. Starting Your First Virtual Machine in oVirt 12. Deploying OpenStack Private Cloud backed by KVM Virtualization 13. Performance Tuning and Best Practices in KVM 14. V2V and P2V Migration Tools Converting a Virtual Machine into a Hypervisor Index

CPU tuning


I would like to reiterate that vCPUs are POSIX threads in the KVM host. You can allocate vCPUs for guest systems according to your needs. However, to get the maximum or optimal performance, it is always better to allocate required virtual CPUs for each guest based on the expected load of the guest operating system. There is nothing wrong with allocating more than is needed; however, it may cause scaling issues in future, when considering the host system as a single unit serving all configured guests.

There is also a misconception that the number of vCPUs defined by all of the guest systems should be less than the total number of CPUs available in the HOST system. To expand further on this thought, if the total number of CPUs available in the HOST system is 32, some people think they can only define eight vCPUs each if they defined four guests in the system. There is no rule like that. Generally speaking, these vCPUs are lightweight processes running in your KVM hosts that get...

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
Visually different images