I saw a question get posted on twitter that kind of intrigues me a little. The question was pretty straight forward. “How many virtual machines should I be able to run on a host?” That is really a fair question in itself but what I find intriguing is that this is the first question he asks. Is this really the first thing administrators think to ask when designing their environment? After all there is no set formula on how many virtual machines you can run on a host. You can be a little more exact when working with VDI because for the most part all the virtual machines would be set up pretty much the same way and the numbers can be a little more predictable. That would not be the case when working with server virtualization. You are going to have servers all with different configurations and amount of resources provisioned to the virtual machines. This variation is what will change your slot count and the amount of virtual machines you can run on the host.
• • 0 Comments
Although virtualization technologies have been a great help to data center managers looking to reclaim power in an overburdened environment, virtualization can also create problems. As IT organizations complete their server virtualization initiatives and as their virtualization management skills mature, use of the physical server power management features and dynamic workload shifting capabilities will increase. This, coupled with increased adoption of server hosted desktop virtualization, will create new opportunities for improving the efficiency of data center power and cooling systems, as well as new challenges for keeping up with increasing demand.
VMware and Citrix are partners – they have just not announced it. Both companies have realized that customers want the market leading application delivery suite (Citrix) to work on the market leading data center virtualization platform (vSphere) and with the cooperation of the partners who implement both solutions have made it happen.
I can remember, in what seems like a really long time ago, about the creation of a new company, Acadia, that will support the coalition of VMware, Cisco and EMC’s vBlock product. I had really long forgotten about the new company that was going to be formed when EMC really started their hiring blitz and campaign to get all the well known talent that EMC could get their hand on. That had been the news and buzz in the industry, as well as a nonstop twitter topic speculation about who was going to be the next person to enroll in Chad’s Army as a vSpecialist. It really appeared that the EMC crew was going to be in the best position to support and sell vBlock technology.
There has been a lot of noise about a negotiations between VMware and Novell, rumors are that it regards the purchase of the SUSE division, now firstly every thing that follows is pure supposition on my part, I have no insider knowledge. now mike has put forward one argument on why a VMware purchase of Novell SUSE assets make very good corporate sense. However I put another idea into the fray.
VMware may buy SUSE from Novell for a host of reasons, one of the most important of which may be that it gets access to Mono and thereby creates a .NET cloud to compete with Microsoft Azure. Paradoxically, we expect that Microsoft will want this to happen.
VMware dominates the enterprise virtualization platform business with vSphere, and is poised to create a vSphere compatible public cloud ecosystem around vCloud. Layering Management software on top of these platforms is a logical progression up the value stack, as is layering an applications platform (vFabric) on top of vSphere and vCloud. VMware’s end user computing strategy seems to be too tied to VDI to be able to break out of the fundamental limitations associated with this approach, and will likely leave the larger question of how to manage the next generation desktop to the previously mentioned startups and perhaps Symantec.
There used to be a FedEx commercial that had a saying “when it just has to be there overnight”. What if we did a play on words and changed the saying to work with Fault-Tolerance and or High Availability. The saying would be something like “when it just has to remain running overnight”.
There seem to be three styles of IO Virtualization (IOV) taking place within the virtual environment. At VMworld, the IO Virtualization companies were out and talking to people about their wares, products, and approaches to IO Virtualization. These three methods are:
* Converged Network Adapters used within Cisco UCS, HP Matrix, etc.
* Attached IOV top of rack devices such as the Xsigo Device
* PCIe Extenders
Each of these provide unique benefits to your virtual environment but which to use? First, we need to know what each of these approaches brings to the table.