What’s going on with virtual containers as a desktop virtualization strategy?
Intel had been – and presumably still is – a major proponent of virtual containers as an alternative to hypervisor-based VDI solutions. I was looking through some older marketing material from Intel and they make a strong case, but there seems to be a lot less momentum in virtual containers than in VDI.
With virtual containers you basically have the operating system and applications created and managed centrally by IT and then streamed to the client, where there is a client-based virtual machine manager (VMM). One of the major advantages of this approach is that it doesn’t require the same type of infrastructure investment as VDI because much of the workload takes place on the client side. Another advantage is mobility, since users can cache their virtual containers for off-network use, then hook back up to the network.
It is my understanding that virtual containers typically mean the use of one operating system, which is a disadvantage versus VDI, but I am not 100 percent sure if this issue has been addressed or is being addressed. Another potential disadvantage is that interactions between applications may be limited.
So what’s the story with virtual containers and what impact will they have in the world of desktop virtualization? I have a feeling someone from Intel may be reading this blog, so perhaps we can generate our first comment(s). Yes?]]>