Virtual Library Posts

After power outage the VM will not power-on and throws the following error:

Object type requires hosted I/O

Login to the ESXi host over ssh.
Browse to the VM folder containing the disk files.

Run the following command:

vmkfstools -x check “test.vmdk”
Disk needs repaired

vmkfstools -x repair “test.vmdk”
Disk was successfully repaired.

Start VM

vExpert 2024 Applications are Open!

vExpert 2022 Applications are Open! Don’t miss out on this opportunity, be sure to apply before January 19th, 2024. The vExpert awards will be announced on February 20th, be a part of the announcement! Current vExperts will need to apply even if you were awarded in the second half.

The VMware wrote this  workaround, so you can manually add the operating system to the list for VMware Update Manager.

1. Connect to your vCenter Server Appliance per SSH and log in
2. Create a backup of the vci-integrity.xml file:

3. Modify the vci-integrity.xml file by opening the file using vi editor:

4. Locate the <vci_vcIntegrity> ….. </vci_vcIntegrity> section
5. Enter edit mode by hitting the insert or the letter i button
6. Before the </vci_vcIntegrity> line, add the following lines, depending on the operating system configured in your virtual machine. If entering both versions of the same OS (ie: Windows 2019 AND 2022), see the below Note section

• For Debian 11 (32 bit):

  <supportedLinuxGuestIds>
    <debian11Guest/>
  </supportedLinuxGuestIds>

• For Debian 11 (64 bit):

  <supportedLinuxGuestIds>
    <debian11_64Guest/>
  </supportedLinuxGuestIds>​​​​​​

• For Red Hat Enterprise Linux 9 (64 bit):

  <supportedLinuxGuestIds>
    <rhel9_64Guest/>  
  </supportedLinuxGuestIds>

Some Linux have same issue, for that follow the list of all supported Linux Guest OS IDs

asianux3Guest
asianux3_64Guest
asianux4Guest
asianux4_64Guest
asianux5_64Guest
centosGuest
centos64Guest
coreos64Guest
debian4Guest
debian4_64Guest
debian5Guest
debian5_64Guest
debian6Guest
debian6_64Guest
debian7Guest
debian7_64Guest
debian8Guest
debian8_64Guest
oracleLinuxGuest
oracleLinux64Guest
rhel7Guest
rhel7_64Guest
rhel6Guest
rhel6_64Guest
rhel5Guest
rhel5_64Guest
rocklinux_64Guest
fedoraGuest
fedora64Guest
sles12Guest
sles12_64Guest
sles11Guest
sles11_64Guest
sles10Guest
sles10_64Guest
opensuseGuest
opensuse64Guest
ubuntuGuest
ubuntu64Guest
otherlinuxguest
otherlinux64guest

Best practices to add in your ESXi if you have this storage.

• To storage Compelant  – esxcli storage nmp satp rule add -s “VMW_SATP_ALUA” -V “COMPELNT” -P “VMW_PSP_RR” -O “iops=3”
• To storage PowerMAx – esxcli storage nmp satp rule add -s “VMW_SATP_SYMM” -V “EMC” -M “SYMMETRIX” -P “VMW_PSP_RR” -O “iops=1”
• To storage Huawei – esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_DEFAULT_AA -P VMW_PSP_RR -c tpgs_off
• To storage IBM – esxcli storage nmp satp set –default-psp VMW_PSP_RR –satp VMW_SATP_SVC
• To storage Dell Unity – esxcli storage nmp satp rule add –satp “VMW_SATP_ALUA_CX” –vendor “DGC” –psp “VMW_PSP_RR” –psp-option “iops=1″ –claim-option=”tpgs_on”
• To storage Huawei  . esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_DEFAULT_AA -P VMW_PSP_RR -O iops=1 -c tpgs_off

The Datastore still appears because there is an active process or an iso mounted/snapshot.

First select your cluster -> right click -> datastore -> and rescan

Second, go to vCenter select the datastore and check Check which host you didn’t unmount on, also you can go to the VM tab of this datastore and check if you have a VM.

Login to ESXi over ssh and check this outpu

lsof | grep name of datastore

Run this esxcli storage filesystem list find storage UUID and send me this output.

lsof | grep storage uuid

Replace the naa.

Run this command vsish -e ls /storage/scsifw/devices/<“naa. id of your datastore”>/worlds/ |sed ‘s:/::’ |while read i;do ps |grep $i;done

Check the lock file/ process file  to unmount the datastore

1. Login to VCSA over ssh
2. Go to folder /usr/lib/vmware-vmafd/bin/
   cd VCSA : /usr/lib/vmware-vmafd/bin/
3. Execute this command
   ./dir-cli user modify –account user_name –password-never-expires
4. Type Administrator@vsphere.local password

This procedure will show you how to identify the HPE ProLiant iLO via ESXi CLI.

1 – Enable SSH on the host you need the ILO
2 – Login to the ESXi host by ssh
3 – Then type cd /opt/hp/tools
4 – Then type ./hponcfg -w /tmp/ilo-conf.txt

In my case the customer removed the vSphere replication appliance, so I needed removed all vsphere replications.

1. Login to ESXi
2. Execute this command to list the VMS
   vim-cmd vmsvc/getallvms | awk ‘$3 ~ /^\[/ {print $1}’
3. Execute this command to remove the flag (you need replace VM id)
   vim-cmd hbrsvc/vmreplica.disable 1011