List VCHs and Obtain Their IDs
You can obtain a list of the virtual container hosts (VCHs) that are running in vCenter Server or on an ESXi host by using the vic-machine ls
command.
The vic-machine ls
command lists VCHs with their IDs, names, and versions.
The vic-machine ls
command does not include any options in addition to the common options described in Common vic-machine
Options.
Prerequisites
You have deployed a VCH. If you have not deployed a VCH, vic-machine ls
returns an empty list.
Procedure
- On the system on which you run
vic-machine
, navigate to the directory that contains thevic-machine
utility. Run the
vic-machine ls
command.- To obtain a list of all VCHs that are running on an ESXi host or vCenter Server instance, you must provide the address of the target ESXi host or vCenter Server.
- You must specify the username and optionally the password, either in the
--target
option or separately in the--user
and--password
options. - If your vSphere environment uses untrusted, self-signed certificates, you must also specify the thumbprint of the vCenter Server instance or ESXi host in the
--thumbprint
option. To obtain the thumbprint of the vCenter Server or ESXi host certificate, runvic-machine
without the specifying the--thumbprint
option. The listing of the VCHs fails, but the resulting error message includes the required certificate thumbprint. You can copy the thumbprint from the error message and runvic-machine
again, including the--thumbprint
option.
$ vic-machine-operating_system ls --target esxi_host_address --user root --password esxi_host_password --thumbprint certificate_thumbprint
$ vic-machine-operating_system ls --target vcenter_server_username:password@vcenter_server_address --thumbprint certificate_thumbprint
Result
The vic-machine ls
command lists the VCHs that are running on the ESXi host or vCenter Server instance that you specified.
<!--
ID PATH NAME VERSION UPGRADE STATUS vm-101 path vch_1 vch_version-vch_build-git_commit Up to date vm-102 path vch_2 vch_version-vch_build-git_commit Up to date [...] vm-n path vch_n vch_version-vch_build-git_commit Up to date-->
ID PATH NAME VERSION vm-101 path vch_1 vch_version-vch_build-git_commit vm-102 path vch_2 vch_version-vch_build-git_commit [...] vm-n path vch_n vch_version-vch_build-git_commit
- The IDs are the vSphere Managed Object References, or morefs, for the VCH endpoint VMs. You can use VCH IDs when you run the
vic-machine inspect
,debug
, anddelete
commands. Using VCH IDs reduces the number of options that you need to specify when you run those commands. The
PATH
value depends on where the VCH is deployed:- ESXi host that is not managed by vCenter Server:
/ha-datacenter/host/host_name/Resources
- Standalone host that is managed by vCenter Server:
/datacenter/host/host_address/Resources
- vCenter Server cluster:
/datacenter/host/cluster_name/Resources
If VCHs are deployed in resource pools on hosts or clusters, the resource pool names appear afterResources
in the path. You can use the information inPATH
in the--compute-resource
option ofvic-machine
commands.
- ESXi host that is not managed by vCenter Server:
- The
VERSION
value shows the version ofvic-machine
that was used to create the VCH. It includes the release version, the build number and the short Git commit checksum.