In my previous article I explained the benefits, and walked through the installation, of VMware vSphere Hypervisor (ESXi). The aim of this article is to outline the patching process, to ensure your virtualisation lab is always up to date with the latest bug fixes, security updates and new features.
Being an enterprise platform, the patching process for the standard (free) version is not immediately obvious. In fact when I first started using the vSphere Client I spent a lot of time hunting for a user friendly update option, I was hoping for something like software update in OS X. Unfortunately this feature simply does not exist, unless you have a fully licensed version with vCenter and Update Manager installed.
Thankfully, there are multiple ways you can apply new patches (for example vSphere Management Assistant), but in my opinion the easiest option is to use the command line. Initially this might sound scary, but trust me the process is very simple and does not require any special software or knowledge.
Getting Started:
As always with VMware vSphere, your best bet is to complete this process using a Windows client, as unfortunately OS X and Linux support is still a little hit and miss.
The first step is to download the patches. To do this head over to the VMware Patch Portal and select "ESXi (Embedded and Installable), 5.0.0". This will list all the available patch bundles.
Download each patch bundle, from the oldest to the newest, but do not unzip them. I recommend creating a folder called "patches".
Once complete, launch the vSphere Client and connect to your host. Start by browsing your primary storage, do this by right clicking the specific datastore from the "Summary" tab and selecting "Browse Datastore".
From the datastore browser click to upload your newly created "patches" folder.
This process may take a few minutes, but once complete all the required patches will be stored on the host, which will make life a lot easier later.
Enable the ESXi Shell and SSH:
To enable the ESXi Shell and SSH simply click on the "Configuration" tab, then select "Security Profile" from the "Software" section. Under "Services", click "Edit".
Select "ESXi Shell" and click "Options > Start". Repeat the process for "SSH".
Preparing VMware vSphere Hypervisor (ESXi):
Before initiating the patching you must first shutdown all of your virtual machines and enter maintenance mode. To do this right click your host and click "Enter Maintenance Mode".
Appling Patches:
Now you are ready to connect to the host using SSH. Any SSH client should work, if you don't already have one I recommend you download Putty (which is free).
Connect using the host IP address (standard ports) and when prompted enter your username (e.g. root) and password (if set).
Now apply each patch (oldest to newest) in turn using the following command:
Each patch will take a little while to install, with no indication of progress. Simply wait for the prompt to re-appear.
Once you have applied all the patches restart the host by typing "reboot".
Finally, once your host has rebooted you must exit maintenance mode before restarting your virtual machines. There is no need to disable the ESXi Shell or SSH services as this will be done automatically.
That's it! You now have a fully up to date version of VMware vSphere Hypervisor (ESXi). The only other thing to keep an eye on is if any of the patches included a new version of VMware Tools, if so you should update each of your virtual machines using the standard process.
I'm a heavy user of virtualisation, both client (VMware Fusion) and datacenter (VMware vSphere). Virtualisation delivers a new level of flexibility to computing, allowing you to run multiple operating system environments on a single hardware platform. I think it's fair to say that virtualisation has had a significant impact in large Enterprise organisations (98% of the fortune 500 use VMware), as well as driven the success of Cloud Computing.
However, I also believe there is a strong case for virtualisation for single users (personal use). For example, anyone who has a need to test different platforms, software or configurations, should definitely take a look, as virtualisation allows you to quickly "spin up" new virtual machines, without significant hardware requirements.
The aim of this article is to outline how you can quickly and easily create a virtualisation lab for free, using "Enterprise Ready" tools from VMware. I will specifically be using VMware vSphere 5.0, which is the industry-leading virtualization platform, that utilises a "bare-metal" hypervisor (ESXi), meaning it installs directly on top of the physical server, without the need for a console operating system (unlike ESX or Hyper-V). This keeps the installation incredibly small (less than 150MB), as well as reduces complexity and improves performance and reliability. For any geeks out there, a high level architecture diagram of ESXi can be seen below.
The key point is that VMware agents have been ported to run directly on the VMkernel, instead of a "heavier" (less stable) console operating system. For more details check out the VMware product comparison page.
The other great thing about VMware vSphere 5.0, is that you can install and use the basic features for free (with no expiration date), which will allow you to run ESXi on a standard 64-bit PC or Server (see minimum specification) and create virtual machines, available for remote access. The free version does have some limitations, for example Enterprise services such vMotion will not be available for use (without additional cost), but it is unlikely any personal user will need these advance features.
Installting VMware vSphere Hypervisor (ESXi) 5.0
First, download VMware vSphere Hypervisor (ESXi) v5.0.x from the VMware website. You will need to signup for a free VMware account if you don't already have one. As part of the download you will also receive a licence key, make sure you make a note of it, as it cannot be registered on the VMware License Portal.
Next you need to burn the 300MB ESXi 5.0 ISO image to a CD. If you are running Windows 7 simply double click the ISO, otherwise I recommend you use ImgBurn.
Once complete, set your PC or Server to boot from the optical drive (BIOS Setting) and initiate the ESXi installation.
Another great thing about ESXi, is the installation is incredibly easy. Simply follow the on screen wizard, selecting the default options. The only part you need to check is the storage options, which will depend on how many storage devices you have connected. For example, if you only have a single internal hard drive, you can proceed with the default settings. Once the wizard has completed, it will warn that the storage will be wiped, before installing ESXi. The entire process should only take a couple of minutes and you will be prompted to reboot at the end.
That's it! ESXi is now installed. However, before you can start setting up virtual machines you will need to specify an IP address and if required, a password. By default ESXi will use DHCP, however it is recommended you specify a static IP address, so that you can easily connect to the server in the future.
Finally, you need to install vSphere Client (part of the original download) on a Windows client (sorry, no Mac OS X support yet). The vSphere Client is used to connect to and manage your ESXi environment. Once the client is installed simply type the IP address, username (default = root) and password (if you set one) to connect. You may be prompted about a certificate warning, but simply click ignore.
You now have full administrator access to your VMware vSphere Hypervisor (ESXi) environment. The first thing you should do is add your licence key, by selecting "ESXi Server > Configuration > Licensed Features > Edit".
You can now start creating virtual machines. Anyone familiar with other VMware products (such as VMware Fusion for the Mac) will be right at home. If you are completely new to the world of virtualisation, VMware have a great evaluation guide, as well as friendly support forums. I'll also be sure to follow-up with more VMware vSphere articles in the future. Watch this space.
I'm a big user of virtualisation, both at home and at work and thankfully when it comes to client virtualisation on the Mac, there are a number of great solutions. Personally, I use VMware Fusion (VMWF), primarily because I am most familiar with VMware products, however Parrelles Desktop and VirtualBox are also very popular solutions.
As I have been using client virtualisation on the Mac from many years, I thought I would post a few hints and tips that I have learnt along the way. Although the information below is primarily based on VMWF, it should also be transferable to other client viurtualisation platforms.
Before starting, the usual disclaimer. These tips are what I have found to work well for me, however as with all technology, your specific configuration may deliver different results. Therefore look at this as a guide to help find what works best for your setup.
Memory (RAM) Allocation:
When it comes to virtual machines, memory (RAM) is very important. When you configure a virtual machine in VMWF you set how much memory you want to assign it (this is a fixed value). However you have to keep in mind that Mac OS X also needs a certain amount of memory to continue to operate (2048MB minimum for Mac OS X Lion). Therefore the number of virtual machines you can run simultaneously is generally defined by how much memory you have. Below I have outlined the minimum amount or memory you should allocate to the guest operating system (note, this is minimum, you may need to assign more for certain tasks).
Windows XP = 1024MB
Windows Vista = 2048MB
Windows 7 = 2048MB
Windows Server = 2048MB
Ubuntu = 1024MB
As a result, if you are running Mac OS X Lion and have 4GB of memory available, then you would be able to run two Windows XP virtual machines or one Windows 7 virtual machine, while maintaining usable performance (the image below shows the VMWF memory options).
Processor Configuration (Multi-Core / x64):
If you have a multi-core Mac, I recommend only assigning half the available cores (seen as processors in VMWF) to the virtual machines, therefore leaving half dedicated to Mac OS X. For example, if you have a dual core Mac, you would only assign one core (processor) to the virtual machines. However, if you have a quad-core Mac, you can assign two cores. The good thing about processor performance is that it can dynamically scale depending on the usage, therefore if you have multiple virtual machines running, but all sitting idle, then the majority of your processing power will be available for use in Mac OS X.
Regarding 32bit vs 64bit guest operating systems, for Windows XP, always use 32bit (as the 64bit version is not well supported). However, for Windows Vista and 7 I recommend you use a 64bit version, as this will enable VMWF to use Intel’s VT hardware extensions, which should perform better for call-heavy workloads.
Storage (IDE vs SCSI):
As a general rule, virtual SCSI drives perform better than virtual IDE drives. However, Windows XP does not come with SCSI support unless you install using the VMWF "Easy Install" option, as this will automatically install the required drivers. You can also manually install the drivers during the installation of Windows XP as they can be downloaded from the VMware support website. Windows Vista and 7 will install natively using SCSI.
Some forums claim that static pre-allocated disks are faster than dynamic disks. Although this might be true, I have not seen any real world difference. Therefore I recommend using dynamic disks, unless storage space really isn't an issue for you.
Other Tips:
Running a file-based virtual machine is much faster than a boot-camp partition. This is because accessing data on the NTFS boot-camp partition is slower than a native HFS+ partition.
Windows Vista is a dog (in more ways than one), therefore avoid using where possible. I recommend both Windows XP or Windows 7.
Always run your virtual machines from the fastest physical storage that you have available (for example, solid state). If you have multiple storage options and all are equal, then run the virtual machines from a secondary disk, as this should improve overall performance.
OptiBay, used for adding additional storage to your MacBook (Pro) is not officially supported by VMWF and has been known to cause significant performance issues. There is currently no known workaround for this issue.
"A magical and revolutionary product", but is it for the enterprise?
In my opinion the iPad is the first tablet computer that actually has some promise. It combines quality custom built hardware with an operating system that was designed from the ground up to be controlled with your finger. This combination is critical to guarantee a great user experience and is something that no other tablet before the iPad has been able to deliver.
I can think of many examples of enterprise users (sales reps, execs, road worriers, etc) that have been searching for an ultra portable, simple to use, robust device, that has enough battery power to last all day. Up to now many have attempted to use small form factor laptops or netbooks to fill this gap, but unfortunately these devices have many limitations, such as poor build quality, poor performance, poor battery life and low resolution screens. Also, almost all of these devices run Windows XP/7 which no matter how Microsoft try and spin it, was simply not designed to be used on this type of device, resulting in constant frustration for the user. As a result you could argue that the iPad is the device everyone has been waiting for.
Unfortunately for all of the iPad's strengths, it does have some weaknesses. The majority of enterprises today are still heavily reliant on Microsoft products, such as Windows (Client & Server), Internet Explorer, Office and OCS. Out of the box, the iPad has support for Exchange, allowing users to access Microsoft's email, calendaring and address book services, however there is no official version of Microsoft Office or Internet Explorer available. There are plenty of third party applications that do offer support for these products, such as Pages, Keynote and Numbers for Office and Atomic Browser which has an Internet Explorer compatibility mode, however these applications lack power features and are not guaranteed to be 100% compatible.
The second big issue is Adobe Flash. It is well known that Apple do not believe in Flash and would prefer the world to make the jump to HTML5. Unfortunately it can take large organisations a long time to move to new technologies and as a result, I expect Flash to be be around for quite a while. There are currently no third party applications that provide true Flash support and there is little hope that Apple will ever allow an official solution.
So, with the lack of enterprise application support, it may seem like the iPad simply isn't up to the challenge. However, thanks to the advances in Desktop Virtualisation there may be a way to get the best of both worlds.
Desktop Virtualisation works by separating the desktop environment from the end users physical machine. As a result the virtual desktop is actually running on a remote central server, instead of locally on the client. The user can work with the virtual desktop like normal, with the only difference being that all the applications, processes and data is stored and run centrally (normally in a data centre). This type of technology has many advantages when it comes to support, management and security, as all the user's data is stored in a secure central location that can easily be accessed by administrators 24x7. Another major positive is that just about any device with a browser can be used to access the virtual desktop, including desktops, laptops, phones, tablets, etc. The only real downside is that a persistent connection must be maintained with the central server, which is fine if you are locally connected (on the LAN), however is more challenging when connecting remotely. Thankfully with 3G and 4G technologies being built into most modern devices (including the iPad) this is becoming less of an issue.
So now that we know what a virtual desktop is, let's see how they could be used on the iPad to remove some of the limitations highlighted earlier. The key players (in my opinion) in virtualisation are VMware and Citrix. Although both companies offer solutions for you to connect to a virtual desktop directly from a browser, due to the closed nature of Safari on the iPad this will not work. As a result you need to rely on specific applications downloaded from the Apple AppStore.
Wyse PocketCloud
VMware have not yet created an official application for the iPad to be able to connect to their virtual environments. However, due to the popularity of VMware products (both consumer and corporate) multiple third party developers have stepped up to the challenge. In my opinion, the best application on the market at the moment (that lets you connect to VMware View 3/4 infrastructure), is Wyse PocketCloud. This application allows you to easily configure (under 5 mins) your VMware View connection and then kick off your virtual session. Once the connection is established you are presented with a full virtual desktop with support for a virtual keyboard (on-screen) or bluetooth keyboard (obviously much easier to type on).
I have already done some testing with Wyse PocketCloud and have been very impressed with the results. Below are some screen grabs of the connection process.
Once you have configured your connection it will be displayed on the "My Computers" page. During my testing I have been connecting over VPN on a 8Mb/s DSL circuit. The loading process takes approximately 20 seconds on average.
Once loaded you are presented with your standard Windows desktop. You can simply tap to click or bring up the full navigation bar by tapping the arrow in the bottom right corner. You can also use multi-touch gestures to pan and zoom.
The navigation bar gives you access to settings, fine pointer, virtual keyboard, right click and return to full screen.
As this is a full virtual environment, all standard Windows applications are available. This image below shows Word 2010 running.
Finally you can see the virtual keyboard, this clearly takes up a lot of screen real estate, however it is surprisingly usable when working on a flat surface. I would still recommend connecting a bluetooth keyboard if you are going to use the virtual environment for a prolonged period.
Keep an eye out for my full video demonstration in the next couple of weeks.
Citrix Receiver for iPad
The second application is official from Citrix, known as Receiver for the iPad. Instead of just offering you a full virtual desktop (like Wyse PocketCloud) it also allows you to customise the experience by granting access to specific applications such as Word, etc, directly from the Citrix workspace. This custom access feels right at home on the iPad, with an intuitive and easy to user navigation system, as well as powerful connection features. The video demo from Citrix below shows the application in action:
In my opinion Citrix receiver feels more polished then Wyse PocketCloud and is very quick and easy to use when accessing any virtual application or document. The application also has some nice iPad specific touches, like being able to use your iPhone or iPod Touch as a track pad whilst connected to the virtual environment. I plan to do some extended testing of the Citrix Receiver over the next few weeks to better understand its strengths and weaknesses. As soon as I have more I will post a follow-up article.
This concludes my first roundup of iPad for the enterprise. So far I have been very impressed with the results, as it would appear the combination of iPad and virtual machine delivers all the strengths of the iPad and iOS platforms, while still providing easy access to the full enterprise environment. As previously mentioned, over the next few weeks I intend to do a deeper dive into both the technologies detailed above and will hopefully post video demonstrations of them both in action.
It looks like I'm not the only one that believes the iPad's limitations for the enterprise can be over come. Bloomberg posted an article today stating that SAP AG, Tellabs Inc. and Daimler AG’s Mercedes-Benz are already using the iPad for tasks as varied as accessing work e-mail, approving shipping orders and calling up on-the-spot auto-finance options.
Last week I introduced Google Chrome OS, the new open-source Operating System based on Linux, from Google. Chrome OS has been designed as a super-fast Operating System that only uses web applications (such as Google Apps) and stores all of your content in "the cloud". It is expected to be officially released some time in 2010. However, because the Operating System is open-source, the pre-beta source code has already been made avilable to the public as part of the Chromium OS project. As a result it is possible for anyone to download the code and compile it to work on any x86 computer. This article will walk you through loading a pre-compilied version of Chrome OS, using VMWare Fusion for the Mac.
A few words of warning before you start. Chrome OS is pre-beta, meaning it's slow, buggy and sometimes simply refuses to work at all. With that in mind let's get started!
To start you will need to download a pre-compiled version of Chrome OS. There are a couple of versions floating about the net, however I recommend you download it from GDGT using the link below:
Once downloaded you need to unzip the package to reveal the .vmdk virtual disk.
Next you need to open VMWare Fusion, I am using version 3 for this guide, although version 2 should also work. If you don't already own Fusion I suggest you download the free 30 day trial to get you started. Once open select "File > New".
From here click "Continue without disc".
You can now select "Use an existing virtual disk" and the browse box shown below will appear. Make sure you select "Share this virtual disk" and highlight your newly unzipped .vmdk virtual disk.
You may then be prompted if you would like to convert the virtual machine. If you are, click "Convert".
As the details of Chrome OS are still a little vague, I suggest you pick "Linux" and the "2.6.x Kernel" to provide the best chance for driver compatibility.
You will now be shown a summary page of your configuration. To give Chrome OS the best chance of working correctly you will need to change a few settings. Click "Customize Settings".
You will now be prompted to give your new virtual machine a name. This can be anything you want.
There are two settings that need to be custom configured, "Network" and "Processors & RAM".
Under "Network" you need to switch to "Bridged". You can leave the interface as "Autodetect".
Under "Processors & RAM" I recommend you allocate at least 1024MB of memory. if you have a Mac with 4GB, then I have found 2048MB to be the sweet spot.
You are now ready to start the your new Operating System.
Once loaded you will be prompted for a username and password. This is your standard Google Account details (xxxx@gmail.com). A very common error at this stage is "Network not connected and offline login fail". if you receive this error you can try to re-select "bridged" network from the VMWare settings and restart the virtual machine. Unfortunately some people have not been able to get past this error. If experience this issue you can login to Chrome OS using the local account details, which are: username: chronos (no password).
You should now have Chrome OS up and running. This first thing you will notice is that the resolution is not ideal. To change this press "Control+Option+T" which will open a terminal shell. From the terminal type:
/usr/bin/xrandr --size 1280x800
The resolution will now be chnaged to "1280x800". To close the terminal press "Control+Option+T".
Thats it! Chrome OS is up and running. So far (like Google Wave) there is not much you can actually do, however it is always nice to get a glimpse of the future.
Thursday, April 5, 2012 at 9:44AM | 
