transparent - Gabes Virtual World

VMware vSphere 4.1 released – What’s new?

13 July, 2010 By Gabrie van Zanten 6 Comments

As many of you expected, the new VMware vSphere version is called VMware vSphere 4.1. The hints have been clear these past few weeks and today it became official. Today was the official release and we can finally start blogging about VMware vSphere’s latest features. In the next few days I will post a number of articles on the new features, starting with a list of new features today.

First thing that will be most noticeable is a change in naming:

- The free ESXi has now been renamed to VMware vSphere Hypervisor (ESXi)

- VMotion is now officially named vMotion

- Storage VMotion is now officially named Storage vMotion [Read more...]

Filed Under: VMware Tagged With: 4.1, ballooning, compression, control, ESX, esxi, fcoe, hypervisor, i/o, iscsi, memory, Memory compression, network i/o control, new, page, sharing, sioc, storage, storage io control, tps, transparent, transparent page sharing, update, vmotion, VMware, VMware vSphere 4.1 released – What’s new, vsphere, Whats New

News from VMware's Partner Exchange Keynote

10 February, 2010 By Gabrie van Zanten 4 Comments

Twitter is a great tool if you’re not in Vegas and still want to know what happened at VMware’s Partner Exchange. All the info posted below is info I picked up from twitter, so be aware that not everything is double checked !!! Please do use the comments section to correct or add info [Read more...]

Filed Under: VMware Tagged With: 2010, compression, drs, Exchange, IO Resource Management, IO-RM, keynote, las vegas, memory, Memory compression, partner, tps, transparent, transparent page sharing, vegas, view, VMware

Memory overcommit in production? YES YES YES

5 January, 2010 By Gabrie van Zanten 20 Comments

There was a good discussion on twitter on memory overcommit and the value of memory overcommit and whether you should or should not use it in production. What struck me in this was that on a subject like this, there is so much misunderstanding although there is a lot of documentation available that can explain the subtle difference between good and bad overcommit of memory.

Memory overcommit, the basics.

In short: When you assign more RAM to your VMs than available in your host.

Good memory overcommit: When you assign more RAM to your VMs than available in your host BUT never cross the line where the amount of RAM that is USED by your VMs is more than available in your host.

Bad memory overcommit: When you assign more RAM to your VMs than available in your host AND cross the line where the amount of RAM that is USED by your VMs is more than available in your host.

Recent Comments

Blogroll