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 Proxmox

You're reading from   Mastering Proxmox Master Proxmox VE to effectively implement server virtualization technology within your network

Arrow left icon
Product type Paperback
Published in Jul 2014
Publisher
ISBN-13 9781783980826
Length 310 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Ahmed Ahmed
Author Profile Icon Ahmed
Ahmed
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Mastering Proxmox
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Dive into the Virtual World with Proxmox FREE CHAPTER 2. Proxmox Under the Hood 3. Shared Storages with Proxmox 4. A Virtual Machine for a Virtual World 5. Network of Virtual Networks 6. Proxmox HA – Zero Downtime 7. High Availability Storage for High Availability Cluster 8. Proxmox Production Level Setup 9. Proxmox Troubleshooting 10. Putting It All Together Index

The virtual machine list file


Located under /etc/pve/.vmlist, the virtual machine list file stores a list of all the virtual machines within the Proxmox cluster. The .vmlist file uses the following format to store the list:

"<vmid>": { "node": "<nodename>", "type": "<vm_type>", "version": <int> }

We have two virtual machines and one template in our basic cluster. The following is the information stored in the .vmlist file:

{
  "version": 24,
  "ids": {
  "121": { "node": "pmxvm01", "type": "openvz", "version": 20 },
  "101": { "node": "pmxvm01", "type": "qemu", "version": 11 },
  "201": { "node": "pmxvm01", "type": "qemu", "version": 22 }}
}

Please note that a VM with ID 201 is a KVM template in our cluster. But the .vmlist file does not show any distinguishable information. One way to separate them is by assigning IDs to all the templates within a particular VM. For example, all the templates can have an assigned VM ID between 501 to 599.

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 £13.99/month. Cancel anytime
Visually different images