Blackforce

To restart the service management port on ESX and ESXi carry out the following commands :

ESX

service mgmt-vmware restart

ESXi

/sbin/services.sh restart

esxcfg-firewall -q ntpClient
esxcfg-firewall -e ntpClient
esxcfg-firewall -q ntpClient

ntpdate -u servername

To use EVC, you must be running ESX 3.5 Update 2 or higher with VirtualCenter 2.5 Update 2 or higher and have compatible processors in your servers. EVC does not allow for migration with VMotion between Intel and AMD processors.

Note: To search for supported EVC CPU types, see the charts below or refer to the WebHCL and search by EVC Modes.

CPU Charts can be found by clicking Here

Had an issue yesterday where once a VM was rebooted you no longer had any network connectivity.

You couldn’t ping the gateway or ping anything.

Running the following resolved the issue.

Start, Run, regsvr32 polstore.dll

Reboot and your away.

Recently we deployed some Windows Server 2008 R2 RDS virtual servers to a customer. All was working well until a number of users were deployed to the servers. The servers would freeze for the users on the server when another user logged in. It would freeze at the preparing local session manager stage

After opening a support call with Microsoft we were instructed to rebuild the server on a physical server. On a physical box the problem went away.

Eventually it was found that adding another CPU to the VM resolved the issue. Vmware were also able to recreate the issue and an official bug has been logged for their product.

Its usual practice to RDP to a Virtualcenter box and then access the Console of Virtual Machines. However today I had a customer where when they went to the console screen of the VMs it just was black. No image was drawn at all.

Restarting the Virtualcenter server and the ESX servers did not resolve the matter.

The solution in the end was to increase the colour depth of the RDP session. With 256 Colours the Console screen is not drawn. Never knew that.

I had an error message come up about a VM:

The redolog of xxxxx.xx.vmdk has been detected to be corrupt. The virtual machine needs to be powered on. If the problem still persists, you need to discard the redolog.

I couldn’t power off the VM and it was stuck in an endless loop prompting me to click okay.

Found a good guide on how to kill the VM without having to power cycle the host.

Read more…