Activar acesso SSH no VMware ESXi

Standard

Para activar o acesso SSH (eu precisei logo para poder fazer o wget de umas ISO’s), basta seguirem o seguinte:

  1. Aceder à consola, e carregar em ALT+F1 para abrir uma consola
  2. Escrever unsupported na janela que vos abre, e carregar ENTER
  3. Aparece um ecran que pede a password, colocar a password, e novamente ENTER
  4. Editar o ficheiro inetd.conf (vi /etc/inetd.conf)
  5. Na linha que começa por # SSH, retirar o #
  6. Gravar o ficheiro
  7. Matar o processo inetd ( executar primeiro “ps | grep inetd” para saber qual o PID do processo, e depois “kill -HUP _PID_” )

E pronto, basta isto.

One thought on “Activar acesso SSH no VMware ESXi

  1. Viet

    Recent VMWare ESXi 3.5 updates will eucenntor issues following reboots with SSH. The problem is that these later updates will attempt to return the VMWare Hypervisor back to a factory default’ state on reboot. To get around this, there is a file stored in /vmfs/volumes/Hypervisor1 folder that is called oem.tgz. Its a TAR GZIP’d file that will contain any files and/or folders that you want replaced into the system after a reboot. This means that even if you modify /etc/inetd.conf to enable SSH, and reboot there is a big chance depending on what version of VMWare ESXi you have installed that it will return it back to the factory default state all the time. However if you place the modified version of this file in that archive, it will do some post processing’ after a reboot, and apply whatever is in the oem.tgz file back to the file system as the last stage of the reboot. This gets around losing SSH on restarts. If you are using SSH keys you will also need to place them in the same file in order for them to be re-applied on restart.If you want to know more about this, do a Google search for VMWare ESXi oem.tgz to find out how to construct such a file and its behavior.

Leave a Reply

Your email address will not be published. Required fields are marked *