Difference between the Vm instance and VMWare VM instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 01:30 AM
Hello everyone,
I would like to know the difference between VM instance and VMWare VM instance. I can see the VMWare VM instance also classified as server or computer based on the OS which is useful to keep a track of the inventory however VM instance not classified as any of the tables (server or computer), and we are losing inventory of VM instances.
If you could share is there any major difference between both VM instance and VMWare VM instance table would be better. if you could share the answers reference with the screenshot would be really helpful and make aware in future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 01:52 AM
1. VM Instance (cmdb_ci_vm_instance)
• Table Name: cmdb_ci_vm_instance
• Classification: This table stores generic virtual machines from any cloud or virtualization platform (AWS, Azure, Google Cloud, VMware, etc.).
• CMDB Hierarchy: It does not inherit from cmdb_ci_computer or cmdb_ci_server, so it is not classified under “Servers” or “Computers”.
• Inventory Impact: Since it doesn’t fall under cmdb_ci_server or cmdb_ci_computer, it may not be included in reports or inventory lists that filter for servers/computers.
• Discovery Source: Typically populated by cloud discovery (AWS, Azure, GCP, etc.).
2. VMware VM Instance (cmdb_ci_vmware_instance)
— Table Name: cmdb_ci_vmware_instance
- Classification: Specifically for VMware-based virtual machines managed via vCenter.
— CMDB Hierarchy: This table inherits from cmdb_ci_computer, which means VMware instances are classified as - Computers or Servers based on OS.
- Inventory Impact: Since it belongs to cmdb_ci_computer, VMware VM instances are included in reports that track servers or computers.
- Discovery Source: Typically populated by VMware vCenter discovery.
✔️ If this solves your issue, please mark it as Correct.
✔️ If you found it helpful, please mark it as Helpful.
—
Shubham Jain

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 01:54 AM
Hi,
cmdb_ci_vm_instance is the parent class for cmdb_ci_vmware_instance. The VMWare class adds additional VMWare-specific attributes.
Could you clarify what you mean by "losing inventory" to VM Instances?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 02:07 AM
Thanks for the clarification.
We are managing all the VMware virtual machines instance in our inventory based on the operating system either it can be a server or Computer.
But Virtual machine instance is not in our inventory
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 03:09 AM - edited 02-28-2025 03:10 AM
In an out of the box instance, VMware Virtual Machine Instance (cmdb_ci_vmware_instance) is a sub-class of the Virtual Machine Instance class (cmdb_ci_vm_instance).
Virtual Machine Instance class (cmdb_ci_vm_instance) is the parent class for all kinds of Virtual Machines:
None of these represents a server or computer, as they do not extend from the computer/server hierarchy.
They represent the virtual "container" that hosts the actual server (eg Windows or Linux).
The last time I looked at ServiceNow Discovery (some time ago) - it created a relationship of "virtualized by" between the VM instance, and the actual Windows/Linux server.