Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I noticed that it is very easy to open up SSH on ESXi 4x and there are no warnings or confirmations that hint at it being unsupported. Does this now mean that it is supported?

I could not find any documentation or related posts discussing newer versions of VMware ESXi. It seems that the "unsupported" warnings went away with version 4x.

share|improve this question
Funny that after two days of digging I found a page talking about "Remote Tech Support" feature here:… . No mention of whether it is supported or not for features like using tools like vmkfstools. – JavaScriptDude Nov 18 '10 at 3:46

Supported for what? As a way to access the esxi host to make permanent changes? No

As a way to log into a host to run diagnostic scripts or make temporary changes in order to workaround a problem? Yes. It's called "Tech Support Mode" because it's for... tech support. I think that the KB article implies that any changes you make without vmware support involved are on your own head. I also think that gone are the days that running an unsupported guest OS and having an unrelated support call resulted in a "get rid of that guest then call us back" type response. From the kb article listed in the question comment(which to me says it all):

"Tech Support Mode is provided for the purposes of troubleshooting and remediation. VMware support may provide directions to use TSM in many forms including but not limited to telephone, E-mail, knowledge base articles, documentation, and remote desktop.

VMware recommends using the vSphere Client or any other VMware Administration Automation Product to perform routine ESXi host configuration tasks that do not involve a troubleshooting scenario. For scripting and automation, VMware recommends using the vCLI, PowerCLI, or the vSphere SDK instead of TSM.

TSM may be required to test and debug pre, post, or first boot scripts that are used in conjunction with the new ESXi 4.1 scripted installation feature. VMware recommends limiting testing and debugging these scripts to non-production environments prior to roll-out into production."

share|improve this answer
That was what I was thinking. I in the process of setting up an OpenSolaris ZFS SAN with iSCSI and was researching using Raw Device Mapping. If SSH is not supported then either is using any command line features via SSH such as vmkfstools. I guess the only options are (1) Don't use RDM and go through VMFS layer or (2) Buy licenced version of ESXi and use vCLI to do RDM or (3) Use another Hypervisor. – JavaScriptDude Nov 19 '10 at 5:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.