The future of virtualisation – Maybe?

So, whilst attending some training on VMware NSX, I stumbled on a concept that I could see being the future of virtualisation.

The concept revolved around a similar concept to the slicing that occurs in NSX to share the responsibilities of the network across the NSX controllers.

If you were to take this up to the highest level and truly virtualise all virtual machines by abstracting them away from the physical hardware, you could then utilise a similar slicing method to have a virtual machine functioning across multiple hosts, just seeing all of the CPU and RAM resources etc. as generic resources.  The virtual machine is therefore not tied to a single host but utilises resources from all of the hosts as required… In theory allowing a virtual machine to have practically unlimited resources assigned to it.  If you need more resources in the cluster, you add another server to the cluster and the virtual machines are then redistributed across the available resources (hosts).  If there was a hardware failure, sufficient resources should be made available to make sure that the virtual machines are not impacted at all… Just like a raid configuration, and then the virtual machines are redistributed around the remaining resources.  Just to clarify that each virtual machine would exist across multiple hosts… Even across all hosts.

Again in theory the resources added to the cluster could come from any vendor utilising any CPU and RAM because all of the resources are abstracted from the hardware.

As a concept this would be completely groundbreaking… In reality, I do not have the technical ability to work out whether this would actually be possible but I like the thought that this could be the future… In a few years time… 

About the Author


I have been in IT for the past 15 years and using virtualisation technologies for around the past 8 years. I started, as quite a lot of people do, working with PCs after playing with such iconic systems like the ZX81, ZX Spectrum and then progressing through 386s, 486s, Pentiums etc. After being headhunted at sixth form to work for a small company based around Hertfordshire, UK. I began working with small businesses and gaining a lot of hardware experience. Three years later, after helping to increase the size of the business, I needed to gain exposure to a larger environment to progress my own career. I joined a large manufacturing company around Electronic Test and Measurement which progressed my skills onto more PC work, hardware work and then onto Server Operating Systems. I progressed again onto a consultancy company based in Reading, UK. Initially working as an engineer performing hardware / software installations for larger companies contracted out to the consultancy company, I moved up into a Consultant position continuing my travel across the UK assisting and providing solutions to companies. I finally moved on again to my current position, working back in Hertfordshire, UK. Again working for a large manufacturing company, this time with over 50,000 users worldwide. I am responsible for the datacenter hardware, the storage environment, the vmware environment and also implementing their new Citrix XenApp farm. My days are busy but also productive, its a friendly environment and in my four years of being with the company, I have seen many changes in technology and infrastructure in use within the company. About the site I started this site as I had been thinking of having more of a presence on the web for a while. On a daily basis, I perform tasks and use tools that others may not use or may not think to do and therefore I thought that I would share some of these experiences and tips with others to help with their day to day work. Currently, my main focus of work is around VMware and Veeam Backup & Replication but hopefully as my tasks progress, I’ll be able to share useful bits of information about other areas of IT as well.

Leave a Reply

Your e-mail address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.