esxcfg-module –s “extended_error_logging=2” <qladriver>
http://communities.vmware.com/message/782916
modinfo /usr/lib/vmware/vmkmod/qla4022.o
Random, usually tech stuff – mostly notes, gotchas, how tos …
esxcfg-module –s “extended_error_logging=2” <qladriver>
http://communities.vmware.com/message/782916
modinfo /usr/lib/vmware/vmkmod/qla4022.o
find /vmfs/volumes/ -name ‘*.vmx’ -exec vmware-cmd -s register {} \;
I’ve done this a number of times and never had a problem, but this may not be a good idea.
The steps are to:
1. Right click and disconnect the ESX host from vCenter.
2. Right click and remove the host you just disconnected from vCenter (may hang VC temporarily in the minute rangeor operation may time out) re-log back into VC, once you are able to it host should be gone from the cluster.
3. Re-add to VC under new cluster
http://support.microsoft.com/kb/193888
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<Service name>
<Service name> = vpxd for VirtualCenter
modify the DependOnService key and add MSSQLSERVER
<log>
<directory>/var/log/vmware/</directory>
<name>hostd</name>
<outputToConsole>false</outputToConsole>
<level>info</level>
<maxFileSize>5242880</maxFileSize>
<maxFileNum>5</maxFileNum>
</log>
esxcfg-advcfg –set 5 /Mem/VMOverheadGrowthLimit
/proc/vmware/config/Mem/VMOverheadGrowthLimit
This can be done using vsish: ‘set /reliability/crashMe/Panic’.
ls -l /scripts/support/bin/vsish*
vmkfstools -C vmfs3 -S “storage” /vmfs/devices/disks/vmhba0:0:0:9
/proc/vmware/config/Misc/ProcVerbose
vmkfstools -D file.vmdk
check /var/log/vmkernel and match against MAC address for the Service Console