Blog

New Features in VMware 5.0

Posted by: Jenna Ipock

When deciding between vSphere version 4 and vSphere version 5 there are many things that you need to think about.  The first question that should come to mind is which version has the best benefits for your network. VMware has really improved in their version 5 edition.  It has many benefits that version 4 didn’t have such as being able to vMotion machines when they have snapshots.  Version 5 allows you to migrate your virtual machines between hosts regardless of whether or not they have snapshots, whereas version 4 only let you migrate machines without snapshots.  When using High Availability (HA) and Disaster Recover System (DRS) in VMware, this can be very beneficial.

vSphere version 5 also comes with what is called Auto Deploy.  Auto Deploy makes deploying hosts easier.   This feature is mostly used for companies that are deploying 50 or more hosts. In version 4 you had to use host profiles to help with deploying hosts, but with version 5 you can now use an image.  From the VMware documentation on www.vmware.com Website you will find that when a host boots for the first time, information about the host is stored in VMware. The information that is stored is “image state, configuration state, dynamic state, virtual machine state, and user input.” (If you go to the VMware Website and click ‘support and documentation,’ you will be able to find detailed information about each item that is stored.)

Version 4 used hardware version 7 for creating virtual machines. The hardware version for virtual machines is explained in detail in the vSphere Basic System Administration vCenter Server 4.0. In the document it says, “The hardware version of a virtual machine indicates the lower-level virtual hardware features supported by the virtual machine, such as BIOS, number of virtual slots, maximum number of CPUs, maximum memory configuration, and other characteristics typical to hardware.” With version 7 you can create new hardware on a virtual machine such as a new hard drive or an NIC.  You can also edit your current settings and possibly increase the memory or CPUs. In version 8 you can edit and create just like in version 7. The main difference in the versions is the maximum configurations have increased in version 8. For instance, you can now use 32 virtual processors and 1TB of memory in your virtual machines where as in version 7 you were limited to 8 virtual processors and 255GB of memory per virtual machine. To learn more about the configuration maximums, you can reference the Configuration Maximum pdfs that VMware provides on their Website.

There are many other features that are now available in vSphere version 5 that can be very beneficial for any company. VMware itself is beneficial to any company looking to save money. VMware helps conserve space in server rooms by eliminating the need for physical servers, and saves money on the power needed for those physical servers.  Depending on how many physical servers you have, you could use as little as two servers for your entire VMware environment.  You can also manage all your virtual servers in your VMware environment through vSphere client.  vSphere client gives you the ability to restart, power down, console into servers, and many other options to manage your servers. You just can’t go wrong when it comes to using VMware in your environment.

 

6

About the Author

Discussion

  1. download  May 17, 2012

    whats your twitter?

    (reply)
  2. Starlene  May 28, 2012

    On page 5 it says VLAN trunking is rerqeuid? Why is that?For example, if you have a dedicated vSwitch0 for kernel and console (and are using the same subnet) and use another, say vSwitch1 for example for guest traffic you would not NEED to use a trunk (at least not on the console / kernel vSwitch adapters).It also states In this example, the management network runs on vSwitch0 as active on vmnic0 and standby on vmnic2. The vMotion network runs on vSwitch0 as active on vmnic2 and standby on vmnic0. You have to specifically define this in your failover policy (it doesn’t show this in the doc, it only briefly mentions setting up active/standby)? Also, on ESXi this would only work if you have separate IPs (possible, but not rerqeuid ) for management and the kernel, so is this also the best practice on vSphere vs running everything on a single IP/network (I’ve seen in the past where best, best recommendations were to separate everything, like using 3 vSwitches, management, kernel, guests, is why I ask).Other than that, great document, always love best practices guides. *8)

    (reply)
    • Kanako  August 6, 2012

      My only problem is that this tciuneqhe doesn’t scale. Once your storage requirements exceed what can be hosted internally with the builtin controller it’s cheaper to buy an array than it is to expand the storage of the nodes. An HP P2000 SAS with dual controllers (or equivalent low end array from your vendor of choice) can be had for less than the licensing cost for two nodes of either the HP P4000 VSA or the VMWare VSA and you don’t end up needing 2x or 3x the number of disks. I really liked the idea of a brick of storage, ram, and compute resources but ultimately the economics fell down when our needs exceeded a fairly small setup. As a techie I’m glad I got to play with an interesting technology but as a manager responsible for my budget I’m definitely not as favorable on the technology as it is priced today.

      (reply)
    • Guilherme  August 6, 2012

      Cost, speed of deployment, and aibtily to simplify support. We put the VSA on Cisco hardware (C210 s) with Cisco switches (2960S’s) and we have a 100% Cisco hardware solution with 100% VMware software. Having seen the vendor finger pointing as to whats wrong happen with a lot of vendors, its nice to know that VMware will have to take ownership for it talking to itself. As for the cost, its only 3k above the cost of essentials plus, so its effectively 1k a node. True it has a lot of limits, but if you want a simple, cost effective no single point of failure enviroment, it can be done for under 40k including hardware and setup labor and be kept within 6U of space for servers and storage.

      (reply)
  3. Aaron  May 28, 2012

    Dear DhanushkaI have some problem on above note. As My klwonedge above two systems that OVM & VMW are use for hardware virtualization. ]I have t any experience about the Microsoft ones. Theose softwares use for the virtualized the hardware and get out the maximum capability of the hardware. In other words those software use for the make several virtual systems not for the software virtualization. For the software virtualization, in world use Citrix. It is virtualized most of softwares but not hardware. In most of Telecommunication organization & airlines use Citrix even Google also.any way its good and fine blog

    (reply)
  4. Whitney Hudler  June 15, 2012

    Hi, i think that i saw you visited my blog so i came to “return the favor”.I’m attempting to find things to enhance my website!I suppose its ok to use some of your ideas!!

    (reply)

Add a Comment

# #