ANy updat e on whether your issue was resolved? I dont see anything in the patch list thats specifically related to this error - can you be a bit more specific. I have the same error on 3.5 serve...
See more...
ANy updat e on whether your issue was resolved? I dont see anything in the patch list thats specifically related to this error - can you be a bit more specific. I have the same error on 3.5 server
Unfortunetly ive experience this error for vmotions on ESX3.5U4. Most of the time i can see from vmkwarning that it cannot connect to the destination host vmotion ip, however i can vmkping from s...
See more...
Unfortunetly ive experience this error for vmotions on ESX3.5U4. Most of the time i can see from vmkwarning that it cannot connect to the destination host vmotion ip, however i can vmkping from source to destination. Painful work around has been to disable and re-enable vmotion on source and destinataion
hi guys, very helpful thread, and really useful cmdlet get-stat.... One question if you can provide some help, im trying to write a script that will save the stats for cpu0 as an a...
See more...
hi guys, very helpful thread, and really useful cmdlet get-stat.... One question if you can provide some help, im trying to write a script that will save the stats for cpu0 as an average for every host in my vc, put them into a table and mail it off to the support team... so far my efforts are pulling back results quite slowly, am i doing something horribly slow here? $hosts = Get-VMHost foreach ($esx in $hosts) { $stats = Get-Stat -Entity (Get-VMHost $esx) -Stat cpu.usage.average -Realtime -MaxSamples 1 $stats | where {$_.Instance -eq "0"} | %{ Write-Host $_.Entity "Core" $_.Instance "avg" $_.Value }}
These PSOD's are at best ambiguous, finding it increasingly difficult to map back to hardware - which is usually vmware's recommendation, 'contact the hardware vendor' smartstart tests nev...
See more...
These PSOD's are at best ambiguous, finding it increasingly difficult to map back to hardware - which is usually vmware's recommendation, 'contact the hardware vendor' smartstart tests never seem to throw any light, even the recommended memtest iso seems hit and miss. Phaedrus1 - dont suppose you remember the cpu testing tool from HP, sounds helpful
Hello - did you find a solution to this. I have been getting the same error. VMWare have said its faulty cpu chip, but having swapped this the error remains to happen regularly. all other hosts a...
See more...
Hello - did you find a solution to this. I have been getting the same error. VMWare have said its faulty cpu chip, but having swapped this the error remains to happen regularly. all other hosts are the same in the cluster, but with no psod's
hi guys - i know i may be asking the obvious but how would one pull back that same information - ie the CPU Reserves and display to screen? Tried a few variants of above code to no avail