SupreetK's Posts

Yes, you should be able to upgrade from ESXi 6.0 U3 to ESXi 6.7. Just ensure to validate the hardware compatibility before upgrading. Below is the upgrade compatibility for your reference - ... See more...
Yes, you should be able to upgrade from ESXi 6.0 U3 to ESXi 6.7. Just ensure to validate the hardware compatibility before upgrading. Below is the upgrade compatibility for your reference - Cheers, Supreet
lihlcnkr​ It should work even for 6.0. Alternatively, run the below command. More details in the link - VMware Knowledge Base vm-support --performance --manifests="HungVM:Coredump_VM" --group... See more...
lihlcnkr​ It should work even for 6.0. Alternatively, run the below command. More details in the link - VMware Knowledge Base vm-support --performance --manifests="HungVM:Coredump_VM" --groups="Hardware Logs Network Storage System Userworld VirtualMachines" --vm="/path/to/vmx" Cheers, Supreet
You have to perform a export-import of the vDS and its configuration. Below links will get you going - Migrating a DVS and Host from one vCenter to another. Migration of a Distributed Switch... See more...
You have to perform a export-import of the vDS and its configuration. Below links will get you going - Migrating a DVS and Host from one vCenter to another. Migration of a Distributed Switch to a new vCenter – Important Things to Know – v(e)Xpertise Cheers, Supreet
Unless there is a licensing constraint at the guest OS level, you can go with either 1 socket + 16 cores or 2 sockets + 8 cores. Cheers, Supreet
I think you can go with Haswell EVC mode - Cheers, Supreet
I don't think there is any restriction with respect to disk and memory. With respect to CPU, you can have a max. of 8 vCPUs per VM. Cheers, Supreet
Uploaded log bundle is not complete. vmkernel.log should report some errors with respect to the local and NFS datastore. Cheers, Supreet
Is it showing for all the VMs? Cheers, Supreet
You will need to fix the PID-CID mismatch from the descriptor files using the KB - VMware Knowledge Base​. With 254 levels of snapshot, it might become cumbersome if the chain is broken at multip... See more...
You will need to fix the PID-CID mismatch from the descriptor files using the KB - VMware Knowledge Base​. With 254 levels of snapshot, it might become cumbersome if the chain is broken at multiple levels. Cheers, Supreet​
While it is loading, do you see any errors in the vmkernel.log? Just to isolate, upgrade the host client to the latest version and check once. Cheers, Supreet
This is applicable for ESXi 6.7 - VMware Knowledge Base​. Currently, the only workaround is to manually restart the SNMP service as and when it stops. As per the known issues in the recently rele... See more...
This is applicable for ESXi 6.7 - VMware Knowledge Base​. Currently, the only workaround is to manually restart the SNMP service as and when it stops. As per the known issues in the recently released ESXi 6.7 U1, looks like this is still an ongoing issue and might be fixed in the upcoming releases - VMware ESXi 6.7 Update 1 Release Notes​ Cheers, Supreet
As already mentioned by dbalcaraz, vmware.log records events related to machine activity, system failures, hardware changes, migrations, status and so on. It helps us in various scenarios such as... See more...
As already mentioned by dbalcaraz, vmware.log records events related to machine activity, system failures, hardware changes, migrations, status and so on. It helps us in various scenarios such as VM going unresponsive, migrations failing, issues related to snapshot, BSOD, etc. In short, anything and everything that is related to the specific VM. Cheers, Supreet
Looks like the hosts are crashing in the RSS and Load Balancer module. Can you disable RSS and monitor the hosts? You can run the below command for all the uplinks one by one and disable RSS - ... See more...
Looks like the hosts are crashing in the RSS and Load Balancer module. Can you disable RSS and monitor the hosts? You can run the below command for all the uplinks one by one and disable RSS - esxcli network nic queue loadbalancer set --rsslb=false -n vmnicX Cheers, Supreet
Is it reporting for all the VMs or just this Windows XP VM? Is this being reported on the VM Summary tab? Cheers, Supreet
You can use the 'Client Device' option - Configure a Client Device Type for the CD/DVD Drive in the vSphere Web Client Add a CD or DVD Drive to a Virtual Machine in the vSphere Web Client - ... See more...
You can use the 'Client Device' option - Configure a Client Device Type for the CD/DVD Drive in the vSphere Web Client Add a CD or DVD Drive to a Virtual Machine in the vSphere Web Client - Select Passthrough Cheers, Supreet
Is there anything mapped to ide0:0? If not, easier option would be to create a new VM with the same specifications (without a disk) and attach the existing disks and other necessary devices to th... See more...
Is there anything mapped to ide0:0? If not, easier option would be to create a new VM with the same specifications (without a disk) and attach the existing disks and other necessary devices to the new VM. Cheers, Supreet
Can you share the complete screenshot of the PSOD screen? Cheers, Supreet
AFAIK, it could be any of the virtual machines (irrespective of the guest OS) running on ESXi, Fusion and Workstation platforms. Cheers, Supreet
This KB should help you identify the boot device - VMware Knowledge Base​​ Cheers, Supreet
From the vCenter flash based web client, right click on the required VM and click on 'Export System Logs'. We see the below options - Cheers, Supreet