Categoría: VMware

Publicado el

How To Install OVFTool on Ubuntu 20.04 with Python3

How To Install OVFTool on Ubuntu 20.04 with Python3

Since I use terraform to clone and provision VMs on ESXi, I need to use VMWare’s ovftool. However, I’ve been having errors lately. The OVFTool wants to install using python2, and I keep getting syntax errors. Seems like it’s using my Python3 install and I can’t get it to install.

If we cannot install the ovftool via the conventional way, we have to find a detour or a workaround to get there. For this particular issue with the failed installation on Ubuntu 20.04, this means extracting the ovftool files from the installation .bundle, copying them to /usr/bin/ and configure an alias for the ovftool executable.

Execute ovftool without installing it

This is how it works step-by-step:

Extract the files and change into directory ovftool (you can name the extracted directory as you want):

sudo ./VMware-ovftool-4.4.1-16812187-lin.x86_64.bundle --extract ovftool && cd ovftool
ls -rtl
total 16K drwxr-xr-x 4 root   root         4,0K Mär  9 14:07 . drwxr-xr-x 5 rguske domain^users 4,0K Mär  9 14:07 .. drwxr-xr-x 9 root   root         4,0K Mär  9 14:07 vmware-installer drwxr-xr-x 6 root   root         4,0K Mär  9 14:07 vmware-ovftool Here’s what’s in it:
$ tree -L 2 . ├── vmware-installer │   ├── artwork │   ├── bin │   ├── bootstrap │   ├── lib │   ├── manifest.xml │   ├── python │   ├── sopython │   ├── vmis │   ├── vmis-launcher │   ├── vmware-installer │   ├── vmware-installer.py │   ├── vmware-uninstall │   └── vmware-uninstall-downgrade └── vmware-ovftool     ├── certs     ├── env     ├── icudt44l.dat     ├── libcares.so.2     ├── libcrypto.so.1.0.2     ├── libcurl.so.4     ├── libexpat.so     ├── libgcc_s.so.1     ├── libgoogleurl.so.59     ├── libicudata.so.60     ├── libicuuc.so.60     ├── libssl.so.1.0.2     ├── libssoclient.so     ├── libstdc++.so.6     ├── libvim-types.so     ├── libvmacore.so     ├── libvmomi.so     ├── libxerces-c-3.2.so     ├── libz.so.1     ├── manifest.xml     ├── open_source_licenses.txt     ├── ovftool     ├── ovftool.bin     ├── README.txt     ├── schemas     ├── vmware.eula     └── vmware-eula.rtf
11 directories, 31 files

Move the vmware-ovftool directory to /usr/bin/:

sudo mv vmware-ovftool /usr/bin/

Make the two files ovftool as well as ovftool.bin executable:

sudo chmod +x /usr/bin/vmware-ovftool/ovftool.bin sudo chmod +x /usr/bin/vmware-ovftool/ovftool

Configure an alias for your used shell to execute it as usual:

alias ovftool=/usr/bin/vmware-ovftool/ovftool
tags : Linux, VMware


Impactos: 0

Publicado el

Habilite VNC en implementaciones de VMware

image.png

This article outlines the steps needed to enable VNC on VMware, so that the VNC console can be used within the Platform9 UI.
Step 1 – Changes Needed on the ESXi Hosts Housing the Virtual Machines

SSH to the ESXi host (not vCenter). We need to open the VNC ports on the ESXi firewall. These steps need to be performed on all the ESX hosts that are part of the clusters authorized with Platform9 controller. An automated script for doing same is coming soon.

chmod 644 /etc/vmware/firewall/service.xml
chmod +t /etc/vmware/firewall/service.xml
vi /etc/vmware/firewall/service.xml

Create a new service block before the end of ConfigRoot tag.

<service id=”new unique id within this file”>
<id>VNC</id>
<rule id=”0000″>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>5900</begin>
<end>6199</end>
</port>
</rule>
</service>

Step 2 – Add Firewall Rules to the ESXi Firewall and Verify that Ports Have Been Opened

On the ESXi host, execute the following commands

esxcli network firewall refresh
esxcli network firewall ruleset set –ruleset-id VNC –enabled true

Verify that the firewall rules were applied and the ports are open by executing the following commands

esxcli network firewall ruleset list
# You should see a rule labelled VNC in the output
esxcli network firewall ruleset rule list
# You should see the details of VNC rule i.e. port range, protocol, direction, etc.

Step 3 – Enable VNC for Existing Virtual Machines (Optional)

To enable VNC console for existing VMs, power off the VM and use one of the following:

Using vSphere Web Client
Click on “edit settings”-> Select the “VM Options” tab->Expand the “Advanced” section-> click on “Edit configuration” and add the settings mentioned at the end of this step
Directly on ESXi Host
Edit the *.vmx file of the corresponding VM and the lines mentioned here.

RemoteDisplay.vnc.enabled = “TRUE”
RemoteDisplay.vnc.port = “<port>” # Port between 5900 and 6199

IMPORTANT NOTES –
1. The key point in the step 3 is to make sure that the port number that you are adding does not collide with any other VM. One way to verify that is to SSH into the ESXi host and run grep on all the *.vmx files and choose a port that is not present in the output

grep “vnc.port” */*/*/*/*.vmx

2. For VNC console to work, the appliance, the ESX host, and the browser where the VNC is being accessed need to have IP connectivity to each other.

Fuente:
https://docs.platform9.com/support/enable-vnc-on-vmware-deployments/

#vmware, #Linux

 

Impactos: 0

Publicado el

Omitir la verificación de memoria en un VMware ESXi 5

image.png
Omitir la verificación de memoria en un VMware ESXi 5
 
Pasos a seguir:

Boot the system from USB Stick with ESXi installer on it.
Once the installer welcome screen shows up, press ALT+F1
Login as “root”, no password.
cd /usr/lib/vmware/weasel/util
Delete upgrade_precheck .pyc (compiled version)
Move precheck.py to precheck.py.old
cp upgrade_precheck.py.old upgrade_precheck.py
chmod 666 upgrade_precheck.py
vi upgrade_precheck.py
Type “/MEM_MIN” and press ENTER
Press “i” for insert
Edit the line to read “MEM_MIN_SIZE= (1*1024–32)”
Press ESC and then type “:w” and ENTER
Press ESC and then type “:q!” and ENTER
ps -c | grep weasel
Note the process id for “python”
kill –9 /<process_id/>
This put me back at the main screen, but you can jump back pressing ALT+F2 if necessary
Continue the install process

 Referencia:
image.png

Impactos: 0

Publicado el

Aliños VMware

vmware

mainMem.useNamedFile = “FALSE”
logging = “FALSE”
isolation.tools.unity.disable=”TRUE”
unity.allowCompositingInGuest=”FALSE”
unity.enableLaunchMenu = “FALSE”
unity.showBadges = “FALSE”
unity.showBorders = “FALSE”
unity.wasCapable = “FALSE”
MemAllowAutoScaleDown = “FALSE”
MemTrimRate = “0”
sched.mem.pshare.enable = “FALSE”
snapshot.disabled = “TRUE”
prefvmx.useRecommendedLockedMemSize = “TRUE”

Impactos: 9

Publicado el

notas ESX-i

vmware

vim-cmd vmsvc/getallvms

Start /MIN /D “C:\Program Files\VMware\VMware Remote Console\” vmrc vmrc://root@<IP>/?moid=<ID>
—————————————————-

Apagar virtual machine

esxcli vm process list

esxcli vm process kill –type= [soft,hard,force] –world-id= WorldNumber

Empezaremos realizando una comprobación de disco, cualquier de las dos posibles opciones siguientes es valida:

vmkfstools -x check /vmfs/volumes/NOMBRE_DATASTORE/NOMBRE_CARPETA/NOMBRE_DISCO.vmdk

vmkfstools –fix check /vmfs/volumes/NOMBRE_DATASTORE/NOMBRE_CARPETA/NOMBRE_DISCO.vmdk

La construcción final que hemos hecho en nuestro laboratorio será la siguiente:

vmkfstools –fix check /vmfs/volumes/Datastore3/SRVDC/SRVDC.vmdk

Disk is error free

Si no se encuentran errores en nuestro disco nos desvolverá el mensaje que podemos ver en nuestro ejemplo.

Continuaremos con las opciones de reparación de un disco virtual como en el caso anterior cualquiera de las dos versiones es totalmente válida:

vmkfstools -x repair /vmfs/volumes/NOMBRE_DATASTORE/NOMBRE_CARPETA/NOMBRE_DISCO.vmdk

vmkfstools –fix repair /vmfs/volumes/NOMBRE_DATASTORE/NOMBRE_CARPETA/NOMBRE_DISCO.vmdk

La construcción final que hemos hecho en nuestro laboratorio será la siguiente:

vmkfstools –fix repair /vmfs/volumes/Datastore3/SRVDC/SRVDC.vmdk

Disk is error free

También tenemos la opción de poder comprobar toda la cadena de disco, así podremos determinar si alguno de los eslabones de la cadena están dañados o existe alguna relación no válida entre padres e hijos.

Para llevar a cabo esta acción usaremos el parámetro –chainConsistent en la construcción que mostramos a continuación

vmkfstools –chainConsistent /vmfs/volumes/NOMBRE_DATASTORE/NOMBRE_CARPETA/NOMBRE_DISCO.vmdk

La construcción final que hemos construido en nuestro laboratorio será la siguiente:

vmkfstools –chainConsistent /vmfs/volumes/Datastore3/SRVDC/SRVDC.vmdk

/vmfs/volumes/58faf513-14e12610-798d-002186282a26/ram

sched.swap.dir
cambiar hora sistema
esxcli system time set -d 24 -H 18 -m 10 -M 07 -y 2017

esxcli hardware clock set -d 24 -H 18 -m 10 -M 07 -y 2017

How to Increase Session Timeout on ESXi 6 & 6.5

To increase the session timeout, all you need to do is change one advanced configuration parameter in the ESXi Host Client Web Interface.

First, log in to the web interface. After doing so, navigate to Host > Manage > System > Advanced Settings. Scroll down or search for the UserVars.HostClient.SessionTimeout key.

Impactos: 3

Publicado el

Habilitar VNC en implementaciones de VMware

vmware

This article outlines the steps needed to enable VNC on VMware, so that the VNC console can be used within the Platform9 UI.
Step 1 – Changes Needed on the ESXi Hosts Housing the Virtual Machines

SSH to the ESXi host (not vCenter). We need to open the VNC ports on the ESXi firewall. These steps need to be performed on all the ESX hosts that are part of the clusters authorized with Platform9 controller. An automated script for doing same is coming soon.

chmod 644 /etc/vmware/firewall/service.xml
chmod +t /etc/vmware/firewall/service.xml
vi /etc/vmware/firewall/service.xml

Create a new service block before the end of ConfigRoot tag.

<service id=”new unique id within this file”>
<id>VNC</id>
<rule id=”0000″>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>5900</begin>
<end>6199</end>
</port>
</rule>
</service>

Step 2 – Add Firewall Rules to the ESXi Firewall and Verify that Ports Have Been Opened

On the ESXi host, execute the following commands

esxcli network firewall refresh
esxcli network firewall ruleset set –ruleset-id VNC –enabled true

Verify that the firewall rules were applied and the ports are open by executing the following commands

esxcli network firewall ruleset list
# You should see a rule labelled VNC in the output
esxcli network firewall ruleset rule list
# You should see the details of VNC rule i.e. port range, protocol, direction, etc.

Step 3 – Enable VNC for Existing Virtual Machines (Optional)

To enable VNC console for existing VMs, power off the VM and use one of the following:

Using vSphere Web Client
Click on “edit settings”-> Select the “VM Options” tab->Expand the “Advanced” section-> click on “Edit configuration” and add the settings mentioned at the end of this step
Directly on ESXi Host
Edit the *.vmx file of the corresponding VM and the lines mentioned here.

RemoteDisplay.vnc.enabled = “TRUE”
RemoteDisplay.vnc.port = “<port>” # Port between 5900 and 6199

IMPORTANT NOTES –
1. The key point in the step 3 is to make sure that the port number that you are adding does not collide with any other VM. One way to verify that is to SSH into the ESXi host and run grep on all the *.vmx files and choose a port that is not present in the output

grep “vnc.port” */*/*/*/*.vmx

2. For VNC console to work, the appliance, the ESX host, and the browser where the VNC is being accessed need to have IP connectivity to each other.

https://docs.platform9.com/support/enable-vnc-on-vmware-deployments/

Impactos: 0

Publicado el

Restaurar un archivo *-flat.vmdk huérfano

Tenemos un archivo huérfano *-flat.vmdk que tiene el contenido completo de un disco y queremos recuperar sus datos.

Pasos:

1.- Nos conectamos al host vSphere via SSH
2.- Navegamos hacia el datastore donde tenemos el archivo *-flat.vmdk.
3.- Hacemos un ‘ls -l’ del fichero para ver su tamaño
4.- Escribimos el siguiente comando:

# vmkfstools -c  tamaño -a lsilogic -d thin temp.vmdk

Donde -c contiene el tamaño del archivo *-flat.vmdk

Donde -a es el controlador virtual (casi siempre es lsilogic)

Y -d crea un disco en formato thin-provisioned con el nombre que le demos (no usar el mismo nombre que el original ya que esto pisará el archivo con un disco de datos en blanco).

5.- Como resultado se crearán los ficheros temp.vmdk y temp-flat.vmdk
6.- Borramos el fichero temp-flat.vmdk que no contiene datos, está en blanco
7.- Renombramos el fichero temp.vmdk al nombre del *-flat.vmdk huérfano que tengamos (ponemos el mismo nombre pero quitando -flat)
8.- Editamos con vi el fichero *.vmdk recién renombrado

Cambiamos la siguiente línea:

# Extent description

RW 524288000 VMFS “temp-flat.vmdk”

Por:
# Extent description
RW 524288000 VMFS “nuestroarchivo-flat.vmdk”

9.- Ya podemos montar nuestro disco en cualquier VM y todos nuestros datos aparecerán.

https://communities.vmware.com/thread/453046

Impactos: 11