Following on from a recent VMware View 4.5 to 4.6 upgrade I thought I would include a list of the resources I used to troubleshoot connectivity issues. First off read the View 4.6 Upgrades guide, this lists out the steps required to upgrade all components of the View infrastructure including how to upgrade the View
vMotion has quite a few requirements that need to be in place before it will work correctly. Here is a list of the key requirements for vMotion to work. Each host must be correctly licensed Each host must meet shared storage requirements Each host must meet the networking requirements Each compatible CPU must be from
VMware View 4.6 VMware View 4.6 is out, and with it come new features. A full list of improvements is available here. In the words of VMware, VMware View is the leading desktop virtualisation solution. It provides a virtualised desktop infrastructure which can leverage existing virtual infrastructures and provide a cost effective centrally managed desktop deployment.
Windows virtual machines require more memory with each passing release and software demands on memory are becoming larger all the time. In a vitual environment it is quite simple to increase the amount of virtual memory granted to a virtual machine, especially with features such as hot add. The ability to dynamically increase the amount
As technology progresses, storage requirements grow. It seems to be a never ending pattern. I remember only a few years ago the maximum configurable LUN size of 2TB seemed huge. Now it is common to have many LUN carvings making up tens of Terabytes of SAN storage. The downside to all this extra storage is
Here is a video of some of the entertainment at the CA/3tera party on the Tuesday night during VMWorld. The entertainer is balancing on a ladder, spinning a tray on his head, whilst his head is on fire. he is also juggling a fire club, an axe and a large knife. Oh and he is
Here as some pictures from VMWorld, including the partner day.
Memory in a virtualised environment is split up in three memory types. Virtual Memory – Allocates memory through a syscall to the operating system. This runs at the application level in the same way on virtual machines as in physical machines Physical Memory – Runs at the OS level. In simplistic terms it uses an
Virtual machines are made up of the following files. vmname.vmx – Config file vmname.vmdk – Describes charateristics vmname-flat.vmdk – (hidden by default) Contains the data vmname.nvram – VM BIOS vmname.log – log file vmware#.log – VMware log file vmname.vswp – Virtual machine swap file on the ESX(i) host vmname.vmsd – snapshot descriptor file Limits per
Having read various books, articles, white papers and best practice guides I have found it difficult to find consistently good advice on vNetwork and physical switch teaming design so I thought I would write my own based on what I have tested and configured myself. To begin with I must say I am no networking