RVTools

What's included

About this module

RVTools is the export almost every vSphere estate already has sitting in a folder. What it does not do is answer the questions people are actually asking about that estate. This module reads the workbook and turns each tab into an answer: vInfo becomes a VM inventory with power states, allocated vCPU and memory, and a guest OS mix; vHost becomes a per-host socket and core topology; vCluster, vDisk, vSnapshot and vDatastore become the hygiene and capacity picture. Nothing is re-keyed and nothing is uploaded to a third party — the workbook is read in your browser and only the columns the analysis reads are sent on.

The licensing figure is the headline, because VMware subscriptions are priced per physical core with a minimum per CPU. Multiplying sockets by cores per socket is the easy part; the part that surprises people is the padding. An estate built on small sockets pays for cores it does not physically have, and the module shows that as its own number — billable cores, physical cores, and the difference — with every host that sits under the minimum named. Both the per-CPU minimum and the minimum order quantity are inputs you can change, and the cost line stays blank until you enter your own negotiated price per core. We will never invent a list price and present it as your budget.

Where a number cannot be trusted, the module says so instead of rounding it into the total. A host whose socket and core columns will not read is excluded from the estate figure and listed by name, because a licensing number quietly missing a host is worse than one that admits a gap. A snapshot whose timestamp will not parse is counted as neither stale nor recent. A datastore with no readable capacity is reported rather than divided by. Every finding carries the reason it was raised, so a threshold you disagree with can be retuned without wondering what else moved.

What you can do with it

• Answer "what will renewal cost us" from an export, with the per-CPU core minimum and your own negotiated rate applied

• Find every snapshot older than your threshold and how much space deleting them returns

• Surface orphaned VMDKs left behind by deleted VMs, and powered-off VMs still holding storage

• Spot VMs configured wider than a host socket, or provisioned far beyond what they ever wrote

• See datastore overcommit and which volumes are closest to full before someone finds out the hard way