Vimsh - Revision history

Wila: Added William's article about vimsh

2009-06-30T13:06:11Z

Added William's article about vimsh

← Older revision		Revision as of 15:06, 30 June 2009
Line 87:		Line 87:

	* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]		* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

			* [http://engineering.ucsb.edu/~duonglt/vmware/#vmware_vimsh William Lam's "VMware's undocumented vimsh"]

	[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]		[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]

Wila: correction on vmware-vimsh

2009-01-30T10:58:36Z

correction on vmware-vimsh

← Older revision		Revision as of 12:58, 30 January 2009
Line 27:		Line 27:
	'''ESX 3.5+'''		'''ESX 3.5+'''
	/usr/bin/vimsh -n -e "command"		/usr/bin/vimsh -n -e "command"
	~~/usr/bin/vmware-vimsh "command"~~
	/usr/bin/vmware-vim-cmd "command"		/usr/bin/vmware-vim-cmd "command"

Line 33:		Line 32:
	/bin/vim-cmd "command"		/bin/vim-cmd "command"

			/usr/bin/vimsh is a symbolic link to the file [[vmware-vimsh]] in the same folder.

	==== List of commands ====		==== List of commands ====

Lamw at 23:47, 5 January 2009

2009-01-05T23:47:01Z

← Older revision		Revision as of 01:47, 6 January 2009
Line 20:		Line 20:
	An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.		An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

	In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:		In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative: vimsh -n -e "command"
	vimsh -n -e <command>
	~~When using~~ ESX ~~embedded (ESXi3~~.5+~~) the~~ command ~~is [[~~vim-cmd~~]] instead~~.		'''ESX 3.0.x+'''
			/usr/bin/vimsh -n -e "command"

			'''ESX 3.5+'''
			/usr/bin/vimsh -n -e "command"
			/usr/bin/vmware-vimsh "command"
			/usr/bin/vmware-vim-cmd "command"

			'''ESXi 3.5+'''
			/bin/vim-cmd "command"



	==== List of commands ====		==== List of commands ====

Wila: fix the alignment now that we use a monospaced font on source

2008-12-30T12:30:40Z

fix the alignment now that we use a monospaced font on source

← Older revision		Revision as of 14:30, 30 December 2008
Line 7:		Line 7:
	Below is some output of the shell that you get to see and the output of the "?" command:		Below is some output of the shell that you get to see and the output of the "?" command:

	~~#vimsh~~
	[/]$ ?		[/]$ ?
	hostsvc/ vmsvc/ csinfo help puload		hostsvc/ vmsvc/ csinfo help puload
	internalsvc/ ? csls pinfo puse		internalsvc/ ? csls pinfo puse
	proxysvc/ argtype csuimport pload quit		proxysvc/ argtype csuimport pload quit
	solo/ ~~cls~~ echo ploadpath sleep		solo/ cls echo ploadpath sleep
	vimsvc/ csimport exit ~~pls~~ source		vimsvc/ csimport exit pls source

Wila at 20:37, 29 December 2008

2008-12-29T20:37:58Z

← Older revision		Revision as of 22:37, 29 December 2008
Line 20:		Line 20:
	An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.		An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

	In recent versions of ESX (ESX3.5+), there's also a command line ~~non interactive~~ version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:		In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
	vimsh -n -e <command>		vimsh -n -e <command>
	When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.		When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.

Wila: Added tip from lamw on using vim-cmd on ESXi

2008-12-29T20:36:17Z

Added tip from lamw on using vim-cmd on ESXi

← Older revision		Revision as of 22:36, 29 December 2008
Line 20:		Line 20:
	An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.		An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

	In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:		In recent versions of ESX (ESX3.5+), there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
	vimsh -n -e <command>		vimsh -n -e <command>
			When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.

	==== List of commands ====		==== List of commands ====

Wila at 05:11, 29 December 2008

2008-12-29T05:11:46Z

← Older revision		Revision as of 07:11, 29 December 2008
Line 25:		Line 25:
	==== List of commands ====		==== List of commands ====

	Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki~~, not sure if that's a smart thing to do...~~)		Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

	Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help.		Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

	[[vimsh: hostsvc/]]		[[vimsh: hostsvc/]]
Line 58:		Line 58:

	This command has its origin as a support shell only.		This command has its origin as a support shell only.
	It is rumored about that it will be supported in one of the upcoming versions of ESX		It is rumored about that vimsh will be supported in one of the upcoming versions of ESX

	==== External links ====		==== External links ====

WikiSysop at 09:20, 14 December 2008

2008-12-14T09:20:15Z

← Older revision		Revision as of 11:20, 14 December 2008
Line 3:		Line 3:
	The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.		The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
	It can be invoked from the shell when logged in as root user as an interactive shell.		It can be invoked from the shell when logged in as root user as an interactive shell.
	You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.		You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

	Below is some output of the shell that you get to see and the output of the "?" command:		Below is some output of the shell that you get to see and the output of the "?" command:
Line 25:		Line 25:
	==== List of commands ====		==== List of commands ====

	Following is a list of the ~~availabled~~ commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)		Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
	Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)
			Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help.

	[[vimsh: hostsvc/]]		[[vimsh: hostsvc/]]
Line 76:		Line 77:
	* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]		* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

	[[Category: ESX]][[Category: SDK]]		[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]

Wila at 09:19, 13 December 2008

2008-12-13T09:19:47Z

← Older revision		Revision as of 11:19, 13 December 2008
Line 75:		Line 75:

	* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]		* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

			[[Category: ESX]][[Category: SDK]]

Wila at 09:12, 13 December 2008

2008-12-13T09:12:18Z

← Older revision		Revision as of 11:12, 13 December 2008
Line 16:		Line 16:


	There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)		There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

	An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.		An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.
Line 34:		Line 34:
	[[vimsh: vimsvc/]]		[[vimsh: vimsvc/]]
	[[vimsh: vmsvc/]]		[[vimsh: vmsvc/]]
			[[vimsh: ?]]
	[[vimsh: argtype]]		[[vimsh: argtype]]
	[[vimsh: cls]]		[[vimsh: cls]]