Memory Compression was introduced in vSphere 4.1. Utilization of compression falls between Ballooning & VMkernel Swap. Pages which would have been swapped out are instead compressed & stored in a compression cache (10% of VM memory) located in the main memory. Access to the page only causes a page decompression which can be an order of magnitude faster than the disk access. This is cool technology!
-Users are stored in the /etc/passwd file -Groups are stored in the /etc/group file -Encrypted passwords for the Users are stored in the /etc/shadow file
If you're a Red Hat Enterprise Linux administrator, this should sound strangely familiar to you. But don't assume ESX is Linux. It's not. More vQuotes
During the installation of ESX, it is extremely important to protect VM data stored on existing volumes. Early versions of ESX would actually destroy LUN data which it discovered during installation. Dominic Rivera outlines several options to protect data, a few of which are automated for unattended installs. Follow the link below and check it out:
http://vmprofessional.com/2009/06/protecting-your-san-luns-during.html More vQuotes
Microsoft Windows Licensing In a Virtual Environment
Windows licenses are tied to physical host hardware, not the VM. This applies to any hypervisor. -A Windows 2008 Datacenter Edition license entitles an unlimited number of Windows VMs on the host. -A Windows 2008 Enterprise Edition license entitles up to 4 Windows VMs on the host. -A Windows 2008 Standard Edition license entitles up to 1 Windows VM on the host. More vQuotes
The maximum virtual disk size allowed in a vSphere virtual machine is 2TB minus 512B. This is true even for VMs living on NFS volumes which aren't restricted by the 2TB -512B VMFS volume size limit. This true for RDMs as well.
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf More vQuotes
Know Thy Open Snapshots Snapshots are wonderful. With this technology comes the responsibility of using it properly and knowing its limitations. Keep constant track of the snapshots that exist in your environment. Leaving a snapshot open can cause slowness and lead to failure for the VMs residing on the snapshot volume.
http://www.boche.net/blog/index.php/2008/12/02/know-thy-open-snapshots/ More vQuotes
By default, VMs which are bound to an internal vSwitch (that is, a vSwitch with no pNIC uplinks) cannot be vMotioned. This behavior can be altered by adding the following to the config flag in the vCenter vpxd.cfg file: [migrate] [test] [CompatibleNetworks] [VMOnVirtualIntranet]false[/VMOnVirtualIntranet] [/CompatibleNetworks] [/test] [/migrate] http://kb.vmware.com/kb/1006701 More vQuotes
Windows Failover Clustering with VMware HA - Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA.
http://vmware.com/pdf/vsphere4/r41/vsp_41_mscs.pdf More vQuotes
A RAID rebuild is the most stressful time period in the life of a drive. This is because the drive is busy servicing IO requests to rebuild the RAID set, while also servicing normal read/write IO requests. A drive is more likely to fail during a RAID rebuild. For this reason, it's a good idea to think about smaller RAID 5 sets, use RAID 6 or RAID-DP, or employ the use of a hot spare drive along with RAID protection. More vQuotes
Convert a standard virtual disk to an RDM with the following commands: For virtual compatibility mode: vmkfstools -I [srcfile] -d rdm: /vmfs/devices/disks/vmhbaW:X:Y:Z /vmfs/volumes/[datastore]/[vmdir]/[vmname].vmdk For physical compatibility mode: vmkfstools -I [srcfile] -d rdmp: /vmfs/devices/disks/vmhbaW:X:Y:Z /vmfs/volumes/[datastore]/[vmdir]/[vmname].vmdk http://kb.vmware.com/kb/3443266 More vQuotes
With vSphere 4.1 being the last version with a Service Console, you will need to learn how to use vMA Appliance 4.1 efficiently. Get to know vi-fastpass & its commands which are used to bind to hosts & execute commands without having to supply a server name & credentials with each command issued. vMA 4.1 eliminates the sudo requirement:
If you are experiencing host or VM networking issues, take a look at VMware KB article 1004109 entitled ESX Server host or virtual machines have intermittent or no network connectivity. This article contains several links to troubleshoot networking issues.
Number of virtual machines per host: ESX(i) 4.1: 320 VMs per host (all cluster feature restrictions lifted) ESX(i) 4.0u1: 320 VMs per standalone host ESX(i) 4.0u1: 256 VMs per host in a DRS cluster ESX(i) 4.0u1: 160 VMs per host in an HA cluster of 8 or less hosts ESX(i) 4.0u1: 40 VMs per host in an HA cluster of 9 or more hosts ESX(i) 3.5u5: 170 VMs per host More vQuotes
On this day in 2006, VMware announced Lab Manager, which enables enterprise software development organizations to more efficiently utilize software development and test lab assets, accelerate software development cycles and increase the quality of delivered software products. Two years later on the same date, version 3.0.1 is released with support for ESX3.5 Updates 3 and 4 More vQuotes
vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
http://vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf More vQuotes
On this day in 2009, VMware, Cisco & EMC introduced the Virtual Computing Environment coalition, a collaboration of 3 IT industry leaders. The VCE is created to accelerate customers’ ability to increase business agility through greater IT infrastructure flexibility, & lower IT, energy & real estate costs through pervasive data center virtualization & a transition to private cloud infrastructures.
vSphere 4.0 was released on 5/21/09 and introduced ~150 new features. vSphere 4.1 was released on 7/13/10 and introduced 150+ new features. That's 300+ features in 418 days... or 1 new feature developed every 1.4 days.
Many people stumble on the accurate definition of a VLAN. Although a convenient analogy, a VLAN is really more than just a subnet. Following is a good summary:
"A VLAN is a logical LAN that provides efficient segmentation, security, & broadcast control while allowing traffic to share the same physical LAN segments or same physical switches." -Scott Lowe, Mastering VMware vSphere 4