A blog for all the virtualization and operating system troubleshooting

If you see the vCenter shell prompt while login to Vcenter root login and if you want vCenter appliance prompt follow as : login to VCSA using root: Enter below command:   chsh -s /bin/appliancesh root Log out from the Appliance Shell. Log in again for the changes to take effect.

 From VMware vSphere webclient Select VM and Edit settings page "Add a new device" and select SCSI controller On the New SCSI controller ->Change Type as "VMware Paravirtual" Save . Now while creating new Disk select this PVSCSI controller for the disk.

 Login to vCenter server Appliance using root credential. Go to path: /usr/lib/vmware-TlsReconfigurator/EsxTlsReconfigurator To Enable TLS 1.2 only to all ESXI hosts under a cluster:          ./reconfigureEsx vCenterCluster -c <Cluster_Name> -u <Administrative_User> -p TLSv1.2            :Vcenter server user name for ex:administrator@vsphere.local To Enable TLS 1.1,1.2 only to a specific host under the vCenter server:      ./reconfigureEsx vCenterCluster -h <ESXI_host_Name> -u <Administrative_User> -p TLSv1.1                      TLSv1.2        :Vcenter server user name for ex:administrator@vsphere.local Reboot ESXI host to commit the protocol change. verify the TLS enabled version             [root@R:~] openssl ciphers -v | awk '{print $2}' | sort | uniq  ...

Login to vCenter server Appliance using root credential. Go to path: cd /usr/lib/vmware-TlsReconfigurator/VcTlsReconfigurator To Enable TLS 1.2 only:           ./reconfigureVc update -p TLSv1.2 To Enable TLS 1.1,1.2 only           ./reconfigureVc update -p TLSv1.1 TLSv1.2 verify TLS Version      root@localhost [ /usr/lib/vmware-TlsReconfigurator/VcTlsReconfigurator ]# ./reco                                                                                                             nfigureVc scan

VMKDUMP: Typically, a partition to collect diagnostic information, also called VMkernel core dump, is created on a local storage device during ESXi Installation Firstly list the core dump file (ssh to ESXI) esxcli system coredump file list [root@1:~] esxcli vm process kill --type=hard -w=1412715 [root@1:~] esxcli system coredump file list Path                                                                                                                Active  Configured        Size ------------------------------------------------------------------------------------------------------------------  ------  ----------  ---------- /vmfs/volumes/5ae54067-fc83bd0a-8833-901b0ed03...

 Unable to power off VM from webclient and ESXCLI Issue: Tried power off/kill/reset from webclient and it hangs Tried from ESXI  CLI with: [root@-s1:~] vim-cmd vmsvc/power.off 323 Powering off VM: Power off failed [root@-s1:~] Solution: SSH to ESXI get world ID of your VM: [root@:~] esxcli vm process list VM1    World ID: 2001025    Process ID: 0    VMX Cartel ID: 315952    UUID: 42 0f 13 30 90 95 b7 41-65 2f d0 37 72 89 ba 0e    Display Name: VM1 Forcefully power off VM: -w =>world ID --type=soft/hard/force [root@1:~] esxcli vm process kill --type=hard -w=1412715 [root@1:~]

 For upgrading VMware VM compatibility or HW version: Login to vCenter Server Select VM and Power OFF Right click VM and select Compatibility                now you can do VM HW version upgrade or schedule for later.

The Unified Extensible Firmware Interface (UEFI)[1] is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the legacy Basic Input/Output System (BIOS) firmware interface  VMware vSphere fully supports UEFI firmware and Secure Boot as part of vSphere 6.5 and newer. When creating a VIrtual Machine that is Windows 10 or Windows Server 2016 and later and you choose it be compatible with ESXi 6.7 and later.  Install new Windows operating system: 1.Select the below option while create VM: 2.Change booting option for Firmware: 3.While booting use EFI Vmware options 4.VM will come up with EFI booting