myTemplate

HEYHEY!! I've just received my first Christmas gift!

This one is from Veeam! I've been waiting for this gift to arrive, as I've registered for the gift a few days/weeks ago.

I'm glad to announce that I've unwrapped it and that it contained Veeam Monitor, "FREE Real time Monitoring for your ESXi".

Apparently the rest of the world that has not registered for the product will hear about it in a few hours. Just hang in there!

Thanks Veeam!

The news is out that VMware has decided to rename what would have been VMware Virtual Infrastructure 4 or VI4 to VMware "vSphere". This is the latest of a series of product name changes that VMware has been making in the past couple of weeks. A while ago, VMware renamed VMware Virtual Desktop Manager to VMware View.

I can't really figure out why they went for the name vSphere. The only reason I can think of is that maybe they felt the need to rename the product to try and make it sound as if it includes the a sphere of products for the entire data centre? Anyway, we just better get used to it. VI4 is out and vSphere is in.

VMware has also announced that vSphere's maximum host RAM will be 1TB and 250GB for the Guest's RAM. A nice addition, however I think it will be a while before we get our servers to have 1TB RAM.

VMware and HP are to integrate HP's BTO (Business Technology Optimization) software with VMware vCenter Lab Manager.

This will support VMware’s contemplated VDC-OS (virtual datacenter operating system) by integrating HP Discovery and dependency Mapping, BTO’s application and infrastructure discovery technologies.

HP’s BTO helps you make sure that every dollar invested in IT, every resource allocated and every application in development or production meets your business goals.

It is an approach to IT management that reduces costs and produces business outcomes by helping your IT leaders:

• Allocate IT spend and resources based on business priorities
• Automate key processes across IT strategy, applications and operations
• Measure IT effectiveness and efficiency from a business perspective

VMware’s VDC-OS is aimed at enabling the use of all types of hardware, including servers, storage and networks in an internal enterprise cloud that acts like one super computer that could automatically move workloads to external clouds when additional capacity is needed.

There is a problem with the with HA in VMware ESX 3.5 Update 3. Virtual Machines may reboot unexpectedly when migrated with VMotion or after a Power On operation. This is only when the Virtual Machine is running on an ESX 3.5 Update 3 Host and the ESX Host has VMware HA enabled with "Virtual Machine Monitoring" option active.To work around this problem: 

Option 1: Disable Virtual Machine Monitoring

1.     Select the VMware HA cluster and choose Edit Settings from the right-click menu.

2.     In the Cluster Settings dialog box, select VMware HA in the left column.

3.     Un-Check the Enable virtual machine monitoring check box.

4.     Click OK.

Option 2: Set hostd hearbeat delay to 0

1.     Disconnect the host from VC (Right click on host in VI Client and select "Disconnect" )

2.     Login as root to the ESX Server with SSH.

3.     Using a text editor such as nano or vi, edit the file /etc/vmware/hostd/config.xml

4.     Set the "heartbeatDelayInSecs" tag under "vmsvc" to 0 seconds as shown here:

<vmsvc>
     <heartbeatDelayInSecs>0</heartbeatDelayInSecs>
     <enabled>true</enabled>
</vmsvc>

5.     Restart the management agents for this change to take effect.

service mgmt-vmware restart

6.     Reconnect the host in VC ( Right click on host in VI Client and select "Connect" )