selfhosted-apps-docker/esxi
2023-04-16 18:52:11 +02:00
..
readme.md update 2023-04-16 18:52:11 +02:00

Esxi

guide-by-example

logo

Purpose

Type 1 hypervisor hosting virtual machines, running straight on metal, managed through web GUI.

ESXi is made by vmware. It is a commercial product part of vSphere, but offers free version when one registers on their site.
The free version has limit of max 2 physical cpus, max 8 vCPU per VM, and no access to API which prevents ease of making backups of the VMs. But for backups there is solution of using ghettovcb script.

ESXi is also considered bit picky when it comes to hardware. Having natively supported network card and disk controller is not given.

gui-pic

Basic settings

Password complexity

  • Host > Manage > System > Advanced settings > Password quality control
    retry=10 min=1,1,1,1,1

New user

  • Add new user
    Host > Manage > Security & users > Users > Add user
    Set name and password.
  • Set permissions for the new user
    Host > Actions > Permissions
    Set the same user as before, pick role

Interface

  • Right top corner > user name
    • Auto-refresh=60
    • Settings, turn off everything - statistics, recent only, welcome message, visual effects

NTP time sync

  • Host > Manage > System > Time & date > Edit NTP Settings
    • Use Network Time Protocol (enable NTP client)
    • Start and stop with host
    • pool.ntp.org
    • Host > Manage > Services > search for ntpd > Start

Hostname and domain

  • ssh in
  • esxcli system hostname set --host esxi-2023
  • if domain on network
    esxcli system hostname set --domain example.local

Network

Should just work, but if there is more complex setup, like if a VM serves as a firewall...
Be sure you ssh in and try to ping google.com to see if network and DNS work.

To check and set the default gateway

  • esxcfg-route
  • esxcfg-route 10.65.26.25

To change DNS server

  • esxcli network ip dns server list
  • esxcli network ip dns server add --server=8.8.8.8
  • esxcli network ip dns server remove --server=1.1.1.1
  • esxcli network ip dns server list

To disable ipv6

  • esxcli network ip set --ipv6-enabled=false

Logs

Documentation

Host > Monitor > Logs

The one worth knowing about

  • shell.log - History of shell commands when SSH in
  • syslog.log - General info of what's happening on the system.
  • vmkernel.log - Activities of esxi and VMs

Will update with some actual use, when I use logs.

Logs from systems in VMs are in >Virtual Machines > Name-of-VM > Monitor > Logs

logs-pic

Backups using ghettoVCB

The script makes snapshot of a VM, copies the "old" vmdk and other files to a backup location, then deletes the snapshot.
This approach, where backup in time is full backup takes up a lot of space. Some form of deduplication might be a solution.

VMs that have any existing snapshot wont get backed up.

Files that are backed up:

  • vmdk - virtual disk file, every virtual disk has a separate file. In webgui datastore browser only one vmdk file is seen per disk, but on filesystem theres blabla.vmdk and blablka-flat.vmdk. The flat one is where the data actually are, the other one is a descriptor file.
  • nvram - bios settings of a VM
  • vmx - virtual machine settings, can be edited

Backup storage locations

  • Local disk datastore
  • NFS share
    For nfs share on trueNAS scale
    • Maproot User -> root
    • Maproot Group -> nogroup

Note the exact path from webgui of your datastore for backups.
Looks like this /vmfs/volumes/6187f7e1-c584077c-d7f6-3c4937073090

Install

  • ssh in to esxi
  • cd /tmp
  • esxcli network firewall ruleset set -e true -r httpClient
  • wget https://github.com/lamw/ghettoVCB/releases/download/2021_10_20/vghetto-ghettoVCB.vib --no-check-certificate
  • esxcli software vib install -v /tmp/vghetto-ghettoVCB.vib -f
  • check ls /opt

Config and preparation

Gotta know basics how to edit files with ancient vi

  • Config file template is in /opt/ghettovcb/ghettoVCB.conf
    Make copy of it
    cp /opt/ghettovcb/ghettoVCB.conf /opt/ghettovcb/ghetto_1.conf
  • Only edit this file, for starter setting where to copy backups
    vi /opt/ghettovcb/ghetto_1.conf
    VM_BACKUP_VOLUME=/vmfs/volumes/6187f7e1-c584077c-d7f6-3c4937073090/Backups
  • Create a file that will contain list of VMs to backup
    touch /opt/ghettovcb/vms_to_backup_list
    vi /opt/ghettovcb/vms_to_backup_list
    OPNsense
    Arch-Docker-Host
    
  • Create a shell script that starts ghetto script using this config for listed VMs
    touch /opt/ghettovcb/bin/ghetto_run.sh
    vi /opt/ghettovcb/bin/ghetto_run.sh
    #!/bin/sh
    
    /opt/ghettovcb/bin/ghettoVCB.sh \
        -g /opt/ghettovcb/ghetto_1.conf \
        -f /opt/ghettovcb/vms_to_backup_list \
        &> /dev/null
    
    Make the script executable
    chmod +x /opt/ghettovcb/bin/ghetto_run.sh
  • for my use case where TrueNAS VM cant be snapshoted while running because of a passthrough pcie HBA card there needs to be another config
  • Make new config copy
    cp /opt/ghettovcb/ghetto_1.conf /opt/ghettovcb/ghetto_2.conf
  • Edit the config, setting it to shut down VMs before backup.
    vi /opt/ghettovcb/ghetto_2.conf
    POWER_VM_DOWN_BEFORE_BACKUP=1
  • edit the run script, add another execution for specific VM using ghetto_2.conf
    vi /opt/ghettovcb/bin/ghetto_run.sh
    #!/bin/sh
    
    /opt/ghettovcb/bin/ghettoVCB.sh \
        -g /opt/ghettovcb/ghetto_1.conf \
        -f /opt/ghettovcb/vms_to_backup_list \
        &> /dev/null
    
    /opt/ghettovcb/bin/ghettoVCB.sh \
        -g /opt/ghettovcb/ghetto_2.conf \
        -m TrueNAS_scale \
        &> /dev/null
    

Execution and scheduled runs

To simply execute:

  • /opt/ghettovcb/bin/ghetto_run.sh

To execute it periodicly cron is used.

  • Make backup of roots crontab
    cp /var/spool/cron/crontabs/root /var/spool/cron/crontabs/root.backup
  • Edit roots crontab to execute the run script at 4:00
    add the following line at the end in cron format
    vi /var/spool/cron/crontabs/root
    0    4    *   *   *   /opt/ghettovcb/bin/ghetto_run.sh
    
    To save read only file in vi use :wq!
  • restart cron service
    kill $(cat /var/run/crond.pid)
    crond

Logs about backups are in /tmp

Restore from backup

Documentation

  • In webgui create a full path where to restore the VM
  • The restore-config-template-file is in /opt/ghettovcb/
    named ghettoVCB-restore_vm_restore_configuration_template Make copy of it
    cp /opt/ghettovcb/ghettoVCB-restore_vm_restore_configuration_template /opt/ghettovcb/vms_to_restore_list
  • Edit this file, adding new line, in which separated by ; are:
    • path to the backup, the directory with date in name
    • path where to restore this backup
    • disk type - 1=thick | 2=2gbsparse | 3=thin | 4=eagerzeroedthick
    • optional - new name of the VM
      vi /opt/ghettovcb/vms_to_restore_list
    "/vmfs/volumes/6187f7e1-c584077c-d7f6-3c4937073090/Backups/OPNsense/OPNsense-2023-04-16_04-00-00;/vmfs/volumes/6378107d-b71bee00-873d-b42e99f40944/OPNsense_restored;3;OPNsense-restored"
    
  • Execute the restore script with the config given as a parameter.
    opt/ghettovcb/bin/ghettoVCB-restore.sh -c /opt/ghettovcb/vms_to_restore_list
  • Register the restored VM.
    If it's in the same location as the original was, it should just go through. If the location is different then esxi asks if it was moved or copied.
    • Copied - You are planning to use both VMs at the same time, selecting this option generates new UUID for the VM, new MAC address, maybe some other hardware identifiers as well.
    • Moved - All old settings are kept, for restoring backups this is usually the correct choice.

Switching from Thick to Thin disks

Kinda issue is that vmdk are actually two files.
Small plain .vmdk that holds some info, and the flat.vmdk with actual gigabytes of data of the disk. In webgui this fact is hidden.

  • have backups
  • down the VM
  • unregister the VM
  • ssh in
  • navigate to where its vmdk files are in datastore
    cd /vmfs/volumes/6187f7e1-c584077c-d7f6-3c4937073090/linux/
  • execute command that converts the vmdk vmkfstools -i "./linux.vmdk" -d thin "./linux-thin.vmdk"
  • zeropunch the image file, so that unused blocks are properly zeroed.
    vmkfstools --punchzero "./linux-thin.vmdk"
  • remove or move both original files
    rm linux.vmdk
    rm linux-flat.vmdk
  • In webgui navigate to the datastore. Use move command to rename thin version to the original name.
    This changes the values in linux.vmdk to point to correct flat.vmdk
  • register the VM back to esxi gui.

Disk space reclamation

If you run VMs with thin disks, the idea is that it uses only as much space as is needed. But if you copy 50GB file to a VM, then deletes it, it's not always seamless that the VMDK shrinks by 50GB too.

Correctly functioning reclamation can save time and space for backups.

  • Modern windows should just work, did just one test with win10.
  • linux machines need fstrim run that marks blocks as empty.
  • Unix machine, like opnsense based on FreeBSD needed to be started from ISO, so that partition is not mounted and executed
    fsck_ufs -Ey /dev/da0p3
    afterwards it needed one more run of vmkfstools --punchzero "./OPNsense.vmdk"
    And it still uses roughly twice as much space as it should.

links