Home > Intel Communities > Open Port IT Community > The Server Room > Blog > Tags > hyper-v

The Server Room Blog

2 Posts tagged with the hyper-v tag
0

Virtualization is the big thing, everybody is doing it - just read the in-flight magazine to see why you should be virtualizing your data center... While it is true that Virtually everyone in the fortune 500 has begun to virtualize their data center, it is also true that most servers are still not virtualized.

i.e. The data center landscape is still mostly an opportunity. The software is mature, there are multiple viable solutions, but there are still many questions about how "best" to proceed.

 

As an enterprise engineer working with enterprise customers, I am inevitably asked where the sweet spot is. The reality is, there isn't one. Or "It Depends". In general larger ( 4 socket servers) provide an edge in efficiency as there are more shared components - board, memory, power supplies, etc. Large servers can also provide more head room if most of your VMs are low utilization, but any of them can spike way up. The launch of Intel's six core Xeon 7400 series based servers ( and their record breaking virtualization performance) have added to the interest - is it time to go big?

What does it depend on?

 

  • How big are your VMs? Machines today are quite powerful. We have seen a 10X growth in compute capacity in just the last 6 years. The application that filled 37% of your 2003 vintage server won't even make a dent in a modern Xeon based server. i.e. Most VMs are much smaller than your server 2 socket or 4 socket. There are still tasks - like decision support that scale as big as your machine will go, but with average enterprise utilization down around 12% ( on old hardware) most physical machines fit tidily inside a VM.

  • How spiky are your VMs ( in resource demand - compute, memory, network)? By doing some resource profiling, you can understand where your servers fit best.

  • How many VMs do you want on each PM(physical machine)? You can put more on 4 socket hardware ( efficiency) but have greater redundancy on a bunch of 2 socket hardware ( depth).

 

 

Fortunately you do not have to solve this linear programming problem before you start. In reality the tools are making it easier you solve. Using your favorite VMM manager (choosing this is another discussion). With Intel's VT Flex Migration Technology you can pool together 1, 2, 4 socket current and future generation Xeon platforms and move the workloads ( automatically, or manually) to optimize your resource utilization.

0 Comments Permalink
0

I had the privilege to get invited to the Microsoft Virtualization Launch event in Bellevue, Washington on September 8, 2008 on occasion of the release of Microsoft Windows Server* 2008. I attended the keynote presentations and a number of technical sessions. I was especially interested in calibrating my experience from the few months before working with Hyper-V as an architect and integrator in putting together a demo that was delivered for the Intel Developer Forum, which took place in San Francisco on August 19-21. Please refer to "[p-11499]" for a detailed account.

 

 

The solidity of the product during the months I worked with it was impressive. I've seen behaviors in previous products are technically correct. However, oftentimes with new products (and also with presumably mature products) the system just checks out for a time, or the results of certain operations are ambiguous, yielding a subjective feeling of "mushiness" that does not inspire confidence. None of this happens with the Hyper-V manager user interface. The response was always crisp and the system was good at informing the user about what is happening. At the outset, if the BIOS settings are not correct for running virtualization, it will remind you in very certain terms to turn on hardware support for virtualization and the execute disable bit, even to the point of asking you to power cycle the system before resuming. The claims by Microsoft engineers during the conference about OS and VMM stability are consistent with my own experience.

 

 

Hyper-V comes with an extensive set of tools designed to facilitate large-scale deployments, yet they are useful to small enterprises. Examples mentioned: Microsoft Assessment and Planning (MAP) and integration with System Center. The available tools support the complete deployment life cycle.

 

 

Microsoft invited Thomas Bittman, a VP and distinguished analyst from Gartner. His vision for virtualization is similar to the one painted extensively a book I co-authored. The alignment of his ideas with those in the book caught my attention. See "[p-11383]". His thesis is that the impact of virtualization comes not from the technology itself, the capability to consolidate workloads and save energy, but from the changes in business models it brings.

 

 

"It is now less about the technology and more about process change and cultural change within organizations," said Mr. Bittman. "Virtualization enables alternative delivery models for services. Each virtualized layer can be managed relatively independently or even owned by someone else, for example, streamed applications or employee-owned PCs. This can require major cultural changes for organizations."

0 Comments Permalink

Filter Blog

By author: By date: By tag: