August, 2010

  • Practice Accelerator for Microsoft® Server Virtualization with Advanced Management

     

     
    clip_image002

    If you’ve been following me on Twitter , You may have seen some recent tweets about Microsoft Practice Accelerator for Server Virtualization and Advance Management which i have been delivering to Microsoft partners. In my opinion its a great workshop and will help the partners in developing a Virtualization practice in their organization and gain expertise to work on end to end Virtualization engagements with their customers.

    Build a Services Practice to Fast Track Your Business

    Practice Accelerator (PA) is a Microsoft offering designed to help partners build a technical services practice around Microsoft solutions. PA is a comprehensive set of reusable tools, resources, and best practices introduced in training delivered via Microsoft Live Meeting. PA enables you to identify customer requirements, analyze their needs, scope projects, plan solution requirements, and deploy Microsoft solutions. Practice Accelerator can help you build your business capacity. The complete, reusable documentation set includes project guides, templates, architecture guidance, and planning and design guides, as well as leave-behind materials for your customers.

    PRACTICE ACCELERATOR FOR SERVER VIRTUALIZATION WITH ADVANCED MANAGEMENT

    Virtualization is a key technology for reducing the cost and complexity of IT management.  Microsoft business customers have reported saving on average almost half a million dollars (U.S.) per year through IT projects using Microsoft virtualization products. As organizations around the world deploy The Microsoft® Server Virtualization with Advanced Management (SVAM) they look to skilled Microsoft partners to assist with their planning and deployments. 

    Designed to help you build a services practice around Microsoft SVAM, Practice Accelerator is a comprehensive set of reusable tools, resources, and best practices introduced with training via Microsoft Live Meeting. Enabling you to successfully identify customer requirements and project scope, analyze customer needs, plan solution requirements, and deploy a solution, Practice Accelerator can help you build your capacity. The complete documentation set includes project guides, templates, architecture guidance, planning and design guides, as well as leave-behind materials for the customer.

    Agenda:

    Day 1
    Module 1: Delivery Management
    Module 2: Component Walk-Through
    Module 3: Best Practices: Discovery Phase
    Day 2
    Module 4: Best Practices: Architecture: Hyper-V ™, Clustering, High Availability (HA)
    Module 5: Best Practices: Sub-system Architecture
    Day 3
    Module 6: Best Practices: Management
    Module 7: Best Practices: Advanced Management
    Day 4
    Module 9: Best Practices: Security and Performance
    Module 10: Tips for Success
    Module 11: Ensuring Value

    For a limited time, these sessions are at no cost. Starting in October, you can use your Advisory Hours to purchase Practice Accelerator.

    REGISTER NOW for the sessions at NO COST!

    Delivery Schedule:

    • Aug 9 – 12, 2010
    • Aug 23-26, 2010
    • Sept 13 – 16, 2010
    • Sep 27 – 30, 2010

    For registration details please contact me @ Iftekhar.hussain@microsoft.com

     


  • Enable Hardware settings in BIOS to run Hyper V

    Hypervserver

    I would be lying if I say that i don't get this question anymore from our customers and partners.

    I just bought a new server and it appears to have a multitude of BIOS options for virtualization. Which BIOS options should be enabled and/or disabled to use with Hyper-V?

    I recently received a well drafted message by our friends in Virtualization product group here in Microsoft. Here is what suggested by Microsoft Virtualization Team with respect to HYPER-V, BIOS & PROCESSOR FEATURES and i cant resist to share it with you all because it makes things so clear and easy.

    Hyper-V RTM/R2 Hardware Requirements                                                                                                                                                                                                                         --

    When it comes to hardware requirements for Hyper-V, the hardware requirements are relatively straightforward and have been mainstream for many years and many generations of systems.

    1. 1. Hyper-V is 64-bit only and thus requires a 64-bit (x64) processor
      1. Windows Server 2008 was the final 32-bit (x86) Windows Server release and Windows Server 2008 32-bit version does not include Hyper-V
    2. 2. Hardware Virtualization Assists* in the form of:
      1. Intel VT-x (initially codenamed Vanderpool)
      2. AMD AMD-V (also called SVM and initially codename Pacifica)
    3. 3. Hyper-V requires Hardware Data Execution Prevention:
      1. Intel refers to it as Execute Disable (XD). This feature must be enabled in the system BIOS.
      2. AMD refers to it as No Execute (NX). This feature must be enabled in the system BIOS.

    Again, these are Hyper-V requirements and Hyper-V will not run without these capabilities.

    *Note: When you enable hardware assisted virtualization (Intel VT or AMD AMD-V) in the BIOS, you must TURN THE SYSTEM OFF. NOT REBOOT. OFF. If you don’t power cycle the system completely, you will not enable hardware assisted virtualization on the majority of systems in the market.

    Hyper-V R2* & SLAT Hardware

    For traditional server virtualization or virtualization desktops without RemoteFX, SLAT hardware is not required, but HIGHLY RECOMMENDED. The use of SLAT capable hardware offers significant performance improvements across the board.

    • Intel refers to this a Extended Page Tables (EPT)
    • AMD refers to this as Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI)

    If there are BIOS option to enable these features (they’re usually on by default), these options should be enabled.

    For virtualizing desktops using RemoteFX, SLAT hardware is REQUIRED. The use of SLAT capable hardware offers significant performance improvements across the board and is especially important when using RemoteFX. These technologies are an extension to the traditional TLB that allow Hyper-V to use the hardware to handle multiple TLBs – one for each virtual machine. This is fundamental requirement for RemoteFX.

    • Intel refers to this a Extended Page Tables (EPT).
    • AMD refers to this as Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI).

    If there are BIOS option to enable these features (they’re usually on by default), these options should be enabled.

    Personally, I wouldn’t purchase any system for virtualization that is not SLAT capable.

    *Note: To take advantage of SLAT hardware, you must be running Windows Server 2008 R2 or later or Microsoft Hyper-V Server 2008 R2 or later. Previous versions (Windows Server 2008/2008 SP2 & Microsoft Hyper-V Server 2008/2008 SP2) do not support SLAT hardware and will simply ignore these hardware capabilities.

    Hyper-V : What to Disable in the BIOS

    There are some hardware features that Hyper-V does not utilize and enabling them will prevent Hyper-V from loading. Specifically, please be sure that:                                                     

    • Intel VT-d is disabled
    • Trusted Execution is disabled

    If either of these options is enabled, Hyper-V won’t launch and errors will be posted to the Event Log.

    ===========================================================================

    Q: I’m trying to run Hyper-V on my system and Hyper-V won’t launch. When I look in the event log I see events such as:

    • · Event ID 41: Hyper-V Launch failed; Either VMX not present or not enabled in the BIOS
    • · Event ID 32: Hyper-V Launch failed; At least one of the processors in this system does not appear to provide a virtualization platform supported by Hyper-V

    I’ve ensured that both:

    • Hardware Assists are enabled (Intel VT or AMD-V)
    • Data Execution Prevention is enabled (Intel XD or AMD NX)

    What am I doing wrong?

    A: It sounds like you’re doing a lot right, but there are a few additional BIOS settings you should check. Please be sure that:

    1. Intel VT-d is disabled
    2. Trusted Execution is disabled

    Hyper-V does not utilize these hardware features and enabling them will prevent Hyper-V from loading.

    ===========================================================================

    Q: I see that Hyper-V requires hardware Data Execution Prevention. What does that mean? What does DEP do?

    A: For more information on DEP, check out this article Data Execution Prevention on MSDN and a useful KB here.

     

    Thanks Virtualization Team for such a great written article, I am sure our customers and partners will find them really useful.

    Do send your feedbacks, comments and suggestions, they are always appreciated.

    Cheers!