The information about the Remote PCs project, the differences between ESXi and Hyper-V and virtualization of graphic station environments have been the most interesting topics during the last two weeks according to our followers.
If you didn’t have the chance to read them, you can find the links to these articles below:
Remote PCs with UDS Enterprise & OpenGnSys
If we have a look at how Microsoft Hyper-V and VMware ESXi work, we see many differences in terms of architecture. However, most virtualization administrators aren’t aware of these differences. In fact, many of them don’t really know how Hyper-V hypervisor works on the host operating system.
A very common misunderstanding about Microsoft Hyper-V is that since Windows operating system is required to install Hyper-V, it operates on the host OS instead of directly on the hardwar
Today we bring over an interesting article written by Larry Smith in which he reports his experience building a home-made NAS for VMware’s vSphere hypervisor.
He had been using so far Nexenta 3.x but, as he had to move to 4.x, the possibility of running a GlusterFS cluster using the two NAS servers that he used for Nexenta was called into question. Learn all the details reading this article.
Our analysis about KVM hypervisor management tools and the cost savings by migrating from a desktop virtualization platform with vSphere to another with oVirt have been the most read articles in our blog during the first half of December.
Below you can find the links to these 3 posts so you don’t lose track of the most outstanding information according to our followers:
VDI cost saving: vSphere to oVirt migration
In previous publications we talked about oVirt and Red Hat Enterprise Virtualization, and today we finish our series of articles about KVM hypervisor management tools talking about OpenStack thanks, once again, to this interesting article by vMiss.net.
If we throw a glance at the matrix support of OpenStack hypervisor, we can see that the only set of drivers tested in Group A is libvirt with KVM, which means that these drivers have been deeply tested and are fully supported. Bearing in mind the warm welcome to OpenStack by the Open Source community, this fact is not surprising at all.
Economic costs may be one of the major obstacles when it comes to deploy a virtual desktop infrastructure. But, if instead of using licensed tools we undertake the project with Open Source tools, the costs drops dramatically.
That was precisely the option chosen by the University of Sevilla, since its goal was to save as much as possible without giving up the best service, performance and availability.
