Esx - Revision history

Tony: /* root account locked */

2026-02-18T11:07:58Z

root account locked

← Older revision		Revision as of 11:07, 18 February 2026
Line 58:		Line 58:
	vim-cmd vmsvc/power.on [vmid]		vim-cmd vmsvc/power.on [vmid]

	== root account locked ==		== ESXi root account locked ==
			Check

			pam_tally2 --user root

			and if that shows recent fails:

	pam_tally2 --user root --reset		pam_tally2 --user root --reset

2025-03-04T09:13:10Z

esxtop

← Older revision		Revision as of 09:13, 4 March 2025
Line 26:		Line 26:

	=== Links ===		=== Links ===
			*[https://www.virten.net/vmware/esxtop/ ESXTOP Guide]
	*[https://communities.vmware.com/docs/DOC-11812 Interpreting esxtop statistics]		*[https://communities.vmware.com/docs/DOC-11812 Interpreting esxtop statistics]
	*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]		*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]

2024-03-21T13:38:03Z

HOWTO

← Older revision		Revision as of 13:38, 21 March 2024
Line 41:		Line 41:
	Set new limit		Set new limit
	vsish -e set /sched/groups/767/memAllocationInMB max=1200		vsish -e set /sched/groups/767/memAllocationInMB max=1200


			==list installed vibs==
			esxcli software vib list

	= FAQ =		= FAQ =

2024-03-21T13:29:17Z

Get memory usage

← Older revision		Revision as of 13:29, 21 March 2024
Line 31:		Line 31:

	=HOWTO=		=HOWTO=
	==~~Get~~ memory usage==		==memory usage==
	vsish -e get /memory/comprehensive		vsish -e get /memory/comprehensive

Line 41:		Line 41:
	Set new limit		Set new limit
	vsish -e set /sched/groups/767/memAllocationInMB max=1200		vsish -e set /sched/groups/767/memAllocationInMB max=1200


	= FAQ =		= FAQ =

2024-03-21T13:27:09Z

← Older revision		Revision as of 13:27, 21 March 2024
Line 30:		Line 30:
	*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]		*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]

			=HOWTO=
			==Get memory usage==
			vsish -e get /memory/comprehensive

			memstats -r group-stats -g0 -l5 -s gid:name:parGid:nChild:min:max:minLimit:conResv:availResv:memSize -u mb 2> /dev/null \| sed -n '/^-\+/,/.*\n/p' \| awk 'NR == 2 \|\| $2 ~ /(vim\|vimuser\|terminal\|ssh)$/ {print $0}'


			vsish -e get /sched/groups/767/memAllocationInMB

			Set new limit
			vsish -e set /sched/groups/767/memAllocationInMB max=1200


	= FAQ =		= FAQ =

2024-03-21T12:14:06Z

← Older revision		Revision as of 12:14, 21 March 2024
Line 6:		Line 6:
	*[https://pubs.vmware.com/vsphere-51/topic/com.vmware.vcli.examples.doc/cli_manage_storage.6.6.html NFS on ESX]		*[https://pubs.vmware.com/vsphere-51/topic/com.vmware.vcli.examples.doc/cli_manage_storage.6.6.html NFS on ESX]
	*[https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/ Adding a disk]		*[https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/ Adding a disk]

			*[https://www.vmwareblog.org/disk-mode-esxi-vm-use/ Disk modes]

			=Storage sense codes=
	*[https://kb.vmware.com/s/article/289902?src=vmw_so_vex_rvand_702 interpreting scsi sense codes]		*[https://kb.vmware.com/s/article/289902?src=vmw_so_vex_rvand_702 interpreting scsi sense codes]
	*[https://www.~~vmwareblog~~.~~org~~/~~disk~~-~~mode~~-~~esxi~~-vm-~~use~~/ ~~Disk modes~~]		*[https://www.virten.net/vmware/vmware-esxi-scsi-sense-code-decoder-v2/ esxi scsi sense decoder]
			Example: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0
			*H: host status
			*D: device status
			*P: plugin status
			Sense data:
			*Sense key
			*Additional sense data


	= Tools =		= Tools =

2023-07-03T07:38:34Z

Identify disks in Linux

← Older revision		Revision as of 07:38, 3 July 2023
Line 42:		Line 42:


	== Identify disks in Linux ==		== Identify disks in Linux guest==

	lsscsi		lsscsi


	== Check if vmdk is in use ==		== Check if vmdk is in use ==

2023-03-21T12:23:30Z

FAQ

2021-09-28T09:13:48Z

← Older revision		Revision as of 09:13, 28 September 2021
Line 45:		Line 45:

	lsscsi		lsscsi


	== Check if vmdk is in use ==		== Check if vmdk is in use ==
Line 50:		Line 51:
	grep vmdk some.vmx		grep vmdk some.vmx

	vmkfstools -D foo.vmdk~~ ?~~		https://blah.cloud/infrastructure/safely-checkremove-orphaned-vmdk-files-from-esxi/
			vmkfstools -D foo.vmdk

2021-09-28T09:04:25Z

← Older revision		Revision as of 09:04, 28 September 2021
Line 17:		Line 17:
	*[https://communities.vmware.com/docs/DOC-11812 Interpreting esxtop statistics]		*[https://communities.vmware.com/docs/DOC-11812 Interpreting esxtop statistics]
	*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]		*[https://kb.vmware.com/s/article/1027901 Checking the queue depth of the storage adapter and the storage device]



Line 40:		Line 41:
	esxcfg-info		esxcfg-info


	== Identify disks in Linux ==		== Identify disks in Linux ==

	lsscsi		lsscsi

			== Check if vmdk is in use ==

			grep vmdk some.vmx

			vmkfstools -D foo.vmdk ?



	== list modules ==		== list modules ==

	esxcli system module list		esxcli system module list