Glassware 2.0 requires a micro hypervisor or what is referred to as a “Microvisor”. A microvisor is not to be confused with a traditional hypervisor which, in addition to a host Operating System (“OS”), requires a Guest OS for applications to run. A Microvisor only pulls in elements of the OS stack needed for the software application to run, and also fills in any gaps that may be present, in particular with applications needing functionality not inherent in whichever OS stack you happen to be using.
It is easier to explain using a concrete example. Let’s consider a PACS (healthcare imaging software) that runs on XP workstations. We can virtualize that PACS application on a Glassware server. Since the Microvisor only uses what it needs from Windows XP, it only uses about 5-10% of XP. Because we know that the application is graphics heavy, we can add a GPU chip to the server and the Microvisor allows for direct access to the chip therefore improving graphics rendering performance. Compare this instance with hypervisors. Hypervisors prevent direct access to the hardware. All access is made through virtual drivers which are cumbersome at best and do not work at worst.
The Glassware 2.0 Microvisor is highly efficient and powerful. It fills in the stack allowing Glassware 2.0 to virtualize anything you want from your Windows and Non- Windows environments. All this while still outperforming any of the hypervisor-based solutions.
You can actually utilize the microvisor for other functions as well. Examples would include management, clustering or orchestration. This approach enables you to maintain performance scalability despite what would otherwise be cumbersome overhead to the system.
Microvisors are an integral part of the overall Glassware 2.0 unique approach to virtualization and an integral component that enables us to virtualize non-windows based applications.