This is provided ‘AS IS’ with no warranties, and confers no rights. Use of included samples are subject to the terms specified at Microsoft
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.
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.
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.
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:
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:
I’ve ensured that both:
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:
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.
We always felt the need of Hardware capacity guidance and sizing information for Terminal Services or Remote Desktop services for Server 2008 R2, Whenever I am engaged in any architectural guidance discussion for RDS deployment i always get a question what needs to be taken into consideration while deciding the hardware configuration and to do capacity planning.
Here are some bullet points which I recommend to my partners and customers to consider:
In addition to that, Microsoft has just released a whitepaper on Capacity Planning in Windows Server 2008 R2.
Download it here
The Remote Desktop Session Host (RD Session Host) role service lets multiple concurrent users run Windows®-based applications on a remote computer running Windows Server® 2008 R2. This white paper is intended as a guide for capacity planning of RD Session Host in Windows Server 2008 R2. It describes the most relevant factors that influence the capacity of a given deployment, methodologies to evaluate capacity for specific deployments, and a set of experimental results for different combinations of usage scenarios and hardware configurations.
You can also use this document for sizing Terminal Services on a Hyper V Platform
Also use the Remote Desktop Load Simulation Tools available at following link to do the load testing for number of users on RDS Server
I hope it helps, Let me know if you have any questions.
If you are following my blog, I discussed about Microsoft VDI solution and how it can proved to be a great solution for organizations to lower their management cost and enable flexible work scenarios such as work from home and hot-desking, increased data security and compliance, as well as easy and efficient management of the desktop OS and applications.
Today I’ll talk about enhancements in Terminal Services in Server 2008 which is now renamed to Remote Desktop Services,
Now RDS, in addition to other Terminal Service roles, provides an platform for companies to implement a centralized desktop strategy and for partners to provide additional innovation.
It introduces the new Remote Desktop Connection Broker – an expansion of the Session Broker in Windows Server 2008 – which provides the administrator with a unified experience for setting up user access to both virtualized desktops (running as a full Windows client OS on top of Microsoft’s virtualization infrastructure) and traditional session-based remote desktops.
Together with Hyper-V and System Center Virtual Machine Manager, the Remote Desktop Connection Broker enables a VDI solution for low-complexity, departmental environments, and a platform for partners who are delivering rich, extensible solutions where heterogeneous client support is a prerequisite, and when enhanced management and scalability is a requirement.
The Remote Desktop Connection Broker it complements other, shared RDS infrastructure components in Windows Server 2008, such as Remote Desktop Web Access or Remote Desktop Gateway. With the Remote Desktop Connection Broker, partners will find an extensive set of APIs that will allow them to continue innovation and deliver added value to customers.
Other important improvements in our virtualization platform in Windows Server 2008 R2, such as Live Migration, will further contribute to making Windows Server 2008 R2 an excellent platform for VDI, improving both availability and scalability of a virtual desktop deployment.
RDS in Server 2008 R2 supports two VDI Scenarios:
1. Personal Virtual Desktops
2. Virtual Desktop Pool
The Architecture of VDI deployment using RDS would look something like this.
Learn More about Microsoft VDI and RDS, Please follow the links below
Isn’t that Interesting, I know you cant wait to do a hands on with Microsoft VDI with RDS in Server 2008 R2.
How to setup a VDI lab with RDS?? I’ll be posting step by step soon.
Please stay tuned.. ;-)
Now you can manage your Virtual Machines hosted on Windows Server 2008 Hyper V from Windows 7 client OS,
Windows 7 comes with an inbuilt Hyper V management Snap In which you need to enable from Turn features on/off.
1. Go to Control Panel.
2. Click on Programs and Features and click on Turn Windows Features on/off
After you turn this feature ON, you can find the Hyper-V Management Console in Administrative Tools via Control Panel.
Let me know how it goes..
Its quite hectic these days in Virtualization world as i am actively involved in planning Practice Accelerator for Virtualization. In addition to that I’ve been engaged in lots of Virtualization opportunities and whenever i speak to customers and partners, I tend to get lot of questions about setting up preferred network for Live Migration on Hyper V based clusters.
Its highly recommended to use Cluster Shared Volume (CSV) while setting up the storage for Live Migration, CSV has following advantages:
It looks like something like the diagram below, You can see in this diagram, that all the three nodes has simultaneous access to the same share running their respective VHD files. In the event of one node failure there is no drive ownership change and hence faster failover.
By default, Cluster Shared Volumes (CSV) and Clustering use a private network with the lowest value for Metric property. To prevent CSV and Clustering from sharing the same network with live migration, the default network order used for live migration is changed so that a network with the lowest value for Metric property is at the bottom of the list of networks for live migration. This will reduce the possibility of CSV, clustering, and live migration using the same network.
This helps ensure live migration speeds by placing live migration traffic in a separate network path.
In the Failover Cluster Manager, right-click on the virtual machine and select Properties:
By selecting the “Network for Live Migration” tab, you can specify what network is used for Live Migration. You can specify multiple networks in order of preference. For me, I normally have my 10 Gb/E network set as the first network.
See this screenshot:
Once you select the appropriate network, you will see the performance enhancement and decreased failover times However your Virtual Machine is always high available while its being migrated.
I hope it helps, please feel free to reach me if you need more information.
We all know about RSAT tool to manage Windows Server remotely from a desktop or Laptop PC. Microsoft has just released brand new version of RSAT tool for Windows 7.
RSAT tool also includes Hyper V manager to manage Windows Server 2008 R2 Hyper V and Hyper V Server 2008 R2 remotely.
How to Enable the Hyper-V Manager from the Remote Server Administration Toolkit (RSAT)
Step 1: Download RSAT from the following link and install
Step 2: Go to Add/Remove Programs.
Step 3: Turn Windows Features On or Off and Enable the Hyper-V Tools as shown below.
Step 4: After enabling the Hyper-V Tools, go to the Administrative Tools in the Start Menu where you will see the Hyper-V Manager. (If you don’t see the Administrative Tools, you can enable this by right clicking on the Start Menu, clicking Properties, click Customize and choose to Display the Administrative Tools in in the Start Menu.)
Or, just type Hyper-V Manager at the Start Menu
And you are good to go..!!
With RSAT for Windows 7, You can manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Windows Server® 2003, from a remote computer that is running Windows 7.
Those who have not tried or used RSAT before, Go for it..!!!
Let me know how that works for you..
We all have seen the great series of products coming out from Microsoft this year, For all you knowledge thirsty out there, who are eager to learn new technologies like Windows 7, Server 2008 R2, Microsoft Virtualization R2 Solution and office 2010 and if you haven’t seen them already here are some of the E Books released by Microsoft and best part is they are all FREE
Download Now Download Now
Download Now Download Now
Let me know what you think.. :)
If you are following my blog, couple of weeks before i posted a blog post on Live Migration Network configuration. Now its time to learn the official way to configure the Live Migration network.
Microsoft has just released Hyper-V: Live Migration Network Configuration Guide.
This guide describes how to configure your network to use the live migration feature of Hyper-V™. It provides a detailed list of the networking configuration requirements for optimal performance and reliability, as well as recommendations for scenarios that do not meet these requirements.
Some of the common questions which are answered in this guide are:
It also talks about Hyper-V live migration network requirements, Identifying the network access needs for live migration and Networking considerations for live migration.
We 'have always felt the need of this kind of best practices document on how to setup a live Migration network which can help in efficient and effective live Migrations in Hyper V Clusters. This document should now help us to get there and design the best Virtual Machine. infrastructure.
Access it here
If you wish to learn more about Microsoft Hyper V R2 Live Migration, Please download the Hyper-V Live Migration Overview & Architecture whitepaper
This document describes the live migration feature of Windows Server® 2008 R2 Hyper-V™ in detail, including how live migration moves running VMs and requirements for implementing live migration.
Hope it helps for now.
As always do send your comments, feedback and suggestions :)
Are you deploying or planning to deploy Hyper V Virtualization in production and need guidelines how you can design the best in class infrastructure with optimum utilization of resources. As a Technology Advisor, I often get the request from customers and partners who are doing real life deployments for best practices and guidelines for Hyper V.
Virtualization product group has done a commendable job to offer some of these best practices documents related to
I have collated some of these documents for your reference in here..
Hyper-V Best Practices Analyzer is now available for Windows Server 2008 R2
Best Practices Analyzer (BPA) is a server management tool that is available in Windows Server 2008 R2. BPA reports best practice violations to the administrator after BPA scans the roles that are installed on Windows Server 2008 R2. Administrators can filter out unnecessary information or exclude results from BPA reports. Administrators can also perform BPA tasks with either the Server Manager GUI, or Windows PowerShell cmdlets
Here are some of the whitepapers you would need to build up a great Virtual Infrastructure with Hyper V.
Best practices: Microsoft Hyper-V Dynamic Data Center in an HP BladeSystem environment
Hyper-V Planning and Deployment Guide
Hyper-V Deployment & Best Practices
Hyper-V Configuration & Deployment Guidance
Virtualization Security Best Practices
Performance Tuning Guidelines for Windows Server 2008- Hyper-V
Hyper-V: Live Migration Network Configuration/best practices Guide
Small Business Server/ Domain Controllers
Best Practices for Using Hyper-V with Windows Small Business Server 2008
Running Domain Controllers in Hyper-V
SharePoint Server Role Recommendations for Virtualized Environments
Virtualization of SharePoint Products and Technologies
Microsoft Virtualization Best Practices for SharePoint
Microsoft Virtualization Best Practices for Exchange
HP recommended configuration for Exchange Server 2010 and Hyper-V R2 for 5,000 users
Exchange Server 2007 and Hyper-V: Best Practices Blog Post
Policies and Recommendations for Exchange Servers in Virtualization Environments
Running SQL in a Hyper-V Environment
Consolidation Guidance for SQL Server
High Performance SQL Server Workloads on Hyper-V
Hope you all find them useful, as always your feedbacks and comments are welcome.
With the words like VDI catching up real fast in IT world, Curosity among customers and partners about this new way of deploying Windows has increased. About 40 percent of the time whenever I am in a conversation with customer and partners that relates to Virtualization, we talk about VDI and what are the best use case for VDI,
Here is Microsoft Definition:
Here are few whitepaper and other resources that we have released recently to help customers understand the VDI solution, Identify if VDI is the best solution for your organization and if it is, then how to do the capacity planning and deployment.
1. Achieving Business Value through Microsoft VDI Together with Session Virtualization: This whitepaper discusses the benefits and considerations when planning a Microsoft® Windows Server® Remote Desktop Services solution and the choices associated with a lowest cost deployment for both Session Virtualization and Virtual Desktop Infrastructure (VDI). DOWNLOAD NOW
2. RD Virtualization Host Capacity Planning in Windows Server 2008 R2 This white paper is intended as a guide for capacity planning of RD Virtualization Host in Windows Server 2008 R2. DOWNLOAD NOW
3. Remote Desktop Services Deployment Guide This guide provides instructions for deploying Remote Desktop Services in a production environment running the Windows Server® 2008 R2 operating system. This guide provides instructions for deploying Remote Desktop Services in a production environment running the Windows Server® 2008 R2 operating system. It is intended for information technology (IT) professionals who want to implement an end-to-end, Remote Desktop Services solution. This guide covers deployment best practices for configuring Remote Desktop Services. DOWNLOAD NOW
4. VDI Licensing: There has been some changes made in VDI licensing from Jul 1, 2010 with respect to VECD, its now known as VDA (Virtual Desktop Access), Lets understand when do you need VDA.
Scenario 1: If you are running Windows OS on the endpoint devices and its covered with Software Assurance, You dont need VDA anymore as accessing a Virtual Desktop is now a added benefit of Software Assurance.
Scenario 2: If the endpoint devices are running non Windows OS or its a thin Client terminal, then you need to purchase VDA for those endpoint devices
Below are couple of resources which can help you with understanding of VDA and VDI Suites.
VDA and VDI suites FAQs
VDA Licensing brochure
Hope it helps, please feel free to send in your feedback and questions.
Bye for now!
If you are read my last Blog post, you are all aware that Microsoft has just released Windows 7 RC for TechNet and MSDN subscribers, and it will be available for general public on May 5th 2009.
Microsoft Virtualization Team today introduced a new feature in Windows 7 where Windows XP Mode is a virtual Windows XP environment that customers of Windows 7 Pro, Windows 7 Ultimate and Windows 7 Enterprise can use to run older Windows XP applications with virtualization technologies such as Windows Virtual PC.
And now Windows XPM and Virtual PC will be new features of Windows 7.
Windows 7 Pro provides Windows XP Mode to run many older Windows XP productivity applications. With Windows Virtual PC, you can run Windows XP applications with a single click, directly from Windows 7 desktop.
Hmm… Isn’t it same as MED-V??
Well.. XPM is targeted for small businesses where there is no IT department.
Businesses with IT Professionals can reduce the cost of deploying and managing Windows Virtual PCs by using Microsoft Enterprise Desktop Virtualization (MED-V) which is part of Microsoft Desktop Optimization Pack.
New Features of Virtual PC for XPM:
Easy setup of Windows XP Mode – Once both the Windows Virtual PC and the virtual Windows XP environment are installed, Windows Virtual PC provides a simple wizard to setup the Windows XP Mode with just a few clicks.
USB Support - Users can access USB devices attached to Windows 7 directly from Windows XP Mode. These devices include Printers and Scanners, Flash Memory/Sticks and External Hard Disks, Digital Cameras and more.
Seamless Applications – Publish and Launch applications installed on Windows XP Mode directly from the Windows 7 desktop, as if they were installed on the Windows 7 itself.
Folder Integration between Windows 7 and Windows XP Mode– Access your Windows 7 Known Folders: My documents, Pictures, Desktop, Music, Video, from inside the virtual windows environment, such as Windows XP Mode
Clipboard Sharing – Cut and paste between your Windows 7 and Windows XP Mode.
Printer Redirection – Print directly to your attached printer from your Windows XP Mode applications either in application mode or desktop mode.
So what is the system requirement to run Windows XP Mode?
You can download the Evaluation Guide of Virtual PC to setup XPM from here
So for all those who have already downloaded Windows 7 RC from TechNet and MSDN sites, go ahead and evaluate this great feature while others will be able to do that after May 5th 2009 when Windows 7 RC releases for general public.
And please do share your feedback and experience while evaluating XPM for Windows 7…
And stay tuned for the lots of exciting news and revelation related to Microsoft Virtualization coming up.. ;-)
Hyper V R2 + SCVMM R2 are better together, Can they be any more better….???
Yes, they can and Teams here at Microsoft are constantly making it better and better than the best.
Today Edwin Yuen, Senior Technical Product Manager at Microsoft's Integrated Virtualization team introduced a much awaited feature in System Center Virtual Machine Manager 2008 R2 called Quick Storage Migration(QSM) in a great post on Microsoft Virtualization official blog.
In addition to Live Migration, I get to hear a lot about storage migration when i interact with our partners and customers, How can they migrate the Hyper V storage (VDHs) from 1 SAN box to another. Lots of customer uses Shared storage like SAN to store their VMs VHDs to create a failover cluster to make high available VMs and when it comes to move the Storage from 1 SAN box to another storage location, that causes a considerable amount of downtime.
Now with System Center Virtual Machine Manager R2 and Hyper V with Server 2008 R2, You can do the storage Migration with less than 1 minute of Downtime.
You know the best part i like about this post and this technology, How it helps our customers to further lower the TCO.
In Edwin’s words,
“ One thing our customers have been telling us loud and clear is that they are very, very happy we are offering Live Migration for FREE with Hyper-V R2. With Quick Storage Migration, we knew we had another opportunity to drive down the costs for storage migration capability that has been largely priced out of the reach of most customers. Specifically, VMware Storage VMotion is only available in their Enterprise/Enterprise Plus SKUs ($2875 & $3495 per processor respectively). Contrast this with the fact that Quick Storage Migration is included with System Center Virtual Machine Manager 2008 R2 both the Enterprise Edition and the Workgroup Edition which will be available for starting at about $500.
For a small five node cluster consisting of two and four processors servers, that would cost at a minimum:
That's customer focus.”
Isn’t this piece of technology so irresistible and adds so much value to your existing investments with so lower cost??
I strong recommend you to please read the full blog post of Edwin Yuen to understand how Microsoft Quick Migrations works and how it can benefit business continuity HERE
And do let me know your feedback and comments. :-)
Yeah.. its been three weeks i have posted anything on my blog, just trying to organize some stuff which keeping me really busy these days..
Anyways.. i don't think i talk enough on this blog about Microsoft VDI aka Virtual Desktop Infrastructure solution.
Virtual Desktop Infrastructure is a delivery solution where administrators can centralize the user desktop with OS like Windows Vista as Virtual Machines on servers in your datacenter and make these Virtual Desktop workspace available to users via Remote Desktops, Terminal Services or through connection broker like Citrix.
Why do we need VDI?
Through virtualization, employees can access their applications and data very safely over a network and the risk of data loss is minimized. On the IT side, virtualization accelerates deployment of new capabilities without needing to acquire new hardware and configure components. It also reduces application testing requirements and compatibility issues and simplifies disaster recovery and compliance.
With Desktop Virtualization, It administrators can decouple layers like Operating System, Application and data from Hardware and store them at centralized servers.
Microsoft VDI solution comprises of following Technologies
• Windows Server® 2008 with Hyper-VTM — provides great value with a reliable virtualization platform and integrated management that enables customers to virtualize their desktop infrastructure.
• System Center Virtual Machine Manager 2008 — simplifies the deployment, provisioning, and management of virtualized desktops.
• Windows Server 2008 Terminal Services — virtualizes the presentation of entire desktops or specific applications in a virtualized desktop.
• Microsoft Application Virtualization (App-V) — is part of the Microsoft Desktop Optimization Pack and delivers desktop applications that are never installed, and are dynamically delivered on demand.
• Windows VistaTM Enterprise Centralized Desktop — is a unique licensing option of Windows Vista for VDI
Microsoft also has a strategic alliance with Citrix to create a Dynamic desktop delivery model. With Citrix Connection broker Virtual Desktops gets created On Demand as user logs in. This way administrators don't have to create Multiple Virtual Machines, they just create a master copy of the Windows Image which gets provisioned as user logs in.
It works something like this.
When user logs in with his thin client PC or Rich Client PC,
So three layers Operating System+Application+Data gets combined together and presented to the user.
This way user always have access to his desktop, his application and his data no matter what device he is using,
He can use any PC in office or even from home PC. he will always have access to his Desktop.
Click here for more information on Microsoft VDI solution.
Check Microsoft Desktop Virtualization Strategy
Also see the Demo
So this was just an Introduction, i will get back with some advance information on Microsoft VDI solution very soon.
And as always, do send me your comments and suggestions..
Microsoft has just released Virtual Lab for Implementing Citrix XenDesktop 4 on Hyper V R2.
This lab is intended for IT Professionals who would like to deliver virtual desktop computers using Microsoft Hyper-V Server, Microsoft System Center Virtual Machine Manager and Citrix XenDesktop.
Users will work through the steps to simulate deploying multiple virtual desktops, and will first capture a reference image using the Citrix Provisioning Server for Desktops. Next, the user will verify that the computer can be booted from a diskless client computer. The user will create multiple virtual machines using the reference computer as a template.
Finally, the user will use the Citrix Desktop Delivery Controller and System Center Virtual Machine Manager to create a group of virtual desktops and deploy them to end devices. At the end of this lab, the user will have worked through all the steps required to implement Citrix XenDesktop using Microsoft System Center Virtual Machine Manager and Microsoft Hyper-V Server.
Access the LAB here
It gives me immense pleasure to let you know that Microsoft is announcing the launch of a Silverlight-based web experience for the Indian Premier League cricket tournament, one of the most popular cricket tournaments in the world. The Indian Premier League (IPL), is a Twenty20 cricket competition created by the Board of Control for Cricket in India (BCCI)
Second season of the IPL starts on Saturday, 18 April (Indian Standard Time), and will be streamed online for the first time in high-definition using Microsoft Silverlight. A 5-minute delay in streaming is expected in India. Highlights and full replays of the matches will be available in South Africa, UK, Ireland, New Zealand and USA on demand, approximately 72 hours after the match.
Cricket is the world’s third most popular spectator sport, with fans in over 120 countries, including India, Pakistan, South Africa, Hong Kong, Singapore, Australia, New Zealand, United Kingdom, the West Indies and even a dedicated following in the United States.
Silverlight has become the platform of choice for delivering live and on demand streaming video of massive sporting events, including the 2008 Beijing Olympics on NBCOlympics.com, 2009 March Madness on Demand with CBSSports.com and the live broadcast of the Masters on AT&T’s Fan Zone.
What IPL Fans can expect?
These high quality and stutter-free online events have demonstrated the platform’s reliability to deliver dynamic media experiences for viewers around the world.
IPL fans can expect this same level of quality and support, including features like interactive scoreboard and statistics display, Deep Zoom, various data feeds such as ball-by-ball commentary, and information about match schedules, weather forecast, pitch reports, team standings, and other stuff. It’s all about keeping fans close to the action no matter where the matches are played.
Silverlight 2.0 has been downloaded and installed on more than 300 million consumer PCs in just the six months since its launch.
Due to local television rights, Live streaming will not be available in South Africa, UK, Ireland, New Zealand and USA. Highlights and full replays of the matches will be available in South Africa, UK, Ireland, New Zealand and USA on demand, approximately 72 hours after the match. A 5-minute delay for the web streaming is expected in India.
WATCH IPL 20-20 STREAMING ON www.iplt20.com
In India, Microsoft will host a live demo session for press across 3 cities - Delhi, Mumbai and Bangalore on 17 April 2009. The sessions will be held at the Microsoft offices in these cities.
Hyper V Team here in Microsoft today announced RC2 release Integration Services for Linux.
Now customer will be able to run following Linux distributions on Hyper V Virtualization platform in addition to SUSE Linux Enterprise 10 SP2
· Red Hat Enterprise Linux (5.2, x86/x64)
· Red Hat Enterprise Linux (5.3, x86/x64)
· SUSE Linux Enterprise Server 11 (x86/x64)
The integration components support the following virtualization platforms:
Read it again – Microsoft contributes code to the Linux kernel under GPL v2!
This is first time in history Microsoft Contributes Linux Drivers to Linux Community, This is really exciting as now customer has a more choice of OS running on Hyper V Platform.
Now that the IC’s will be a part of the Linux kernel, other distributions that chose to pick these up will be compatible with Hyper-V. A customer will have to work with their Linux distribution vendor for support.
Customers can obtain the Linux IC’s via access to the Microsoft Connect program: https://connect.microsoft.com/SelfNomination.aspx?ProgramID=1863&pageType=1&SiteID=495
Here is Microsoft Press Release.
REDMOND, Wash., July 20, 2009 — Today, in a break from the ordinary, Microsoft released 20,000 lines of device driver code to the Linux community. The code, which includes three Linux device drivers, has been submitted to the Linux kernel community for inclusion in the Linux tree. The drivers will be available to the Linux community and customers alike, and will enhance the performance of the Linux operating system when virtualized on Windows Server 2008 Hyper-V or Windows Server 2008 R2 Hyper-V.
I just cant stop talking about never ending list of enhancements in recently released Server 2008 R2 RC, I'll continue the bandwagon with some of new functionalities in this release.
If you have just joined the party, please look at the other enhancements i talked about earlier here, here and here
Today I’ll communicate the message from our Windows Clustering Team here in Microsoft about Clustering enhancements in Server 2008 R2 from the Hyper V perspective.
1. No Automatic Failover and Restart When VM is Shutdown: We have seen in BETA that if you shutdown a Virtual Machine in a Clustered environment through Hyper V Manager, Failover Cluster automatically restarts it on a different node, its a great feature and intended behavior of Failover clustering. But sometimes you may really want to shutdown your VM without having it restarted. Now its POSSIBLE with RC.
Now, when you shut down a VM for Hyper-V Manager, the VM resource is marked as offline and Failover Clustering does not restart it. This default behavior can be changed to mark the virtual machine resource as failed from the ‘Settings’ dialog of the virtual machine resource property in Failover cluster manager. This change provides better control to enterprise administrator and provides more consistent behavior.
2. VM Settings from Cluster Manager:
Directly from the Failover Cluster Manager console, you can now make changes to VM settings. When using the Failover Cluster Manager to change the VM settings, it will automatically refresh the VM’s configuration. However, if you change the settings using Hyper-V manager, you still must select the VM in Cluster Manager and choose ‘more actions’ -> ‘Refresh virtual machine configuration’ to ensure that the configuration for the VM in the cluster is correct.
For a clustered VM, changing the VM settings from Cluster Manager is the recommended way to manage configuration changes. This will ensure the VM configuration is refreshed in the cluster.
3. Live Migration default Network Order
Now in RC, the default order of networks for live migration (LM) has been changed. By default, Cluster Shared Volumes (CSV) and Clustering use a private network with the lowest value for Metric property. To prevent CSV and Clustering from sharing the same network with live migration, the default network order used for live migration is changed so that a network with the lowest value for Metric property is at the bottom of the list of networks for live migration. This will reduce the possibility of CSV, clustering, and live migration using the same network. This helps ensure live migration speeds by placing live migration traffic in a separate network path.
4. Auto Start
With RC, we added a new capability called “Auto Start” to manage your cluster environment more efficiently. “Auto Start” allows you to change the default VM failover behavior. If the VM Auto Start option is set to ‘No’ when a cluster node fails, the VM will not automatically restart.
The ‘Auto Start’ setting can be set as ‘No’ on a group of less important VMs (default value is yes). This ensures that during a node failure, the more important VMs will start if there are limited resources on the remaining nodes.
5. Connect to VM from Cluster Manager
Now, from Failover Cluster Manager, you can ‘Connect…’ to the Virtual Machine like you can from Hyper-V Manager. It doesn’t matter what node you are running Failover Cluster Manager on. It can connect to any VM that is in the cluster.
Note: If you modified the VM configuration from Hyper-V Manager or connected to the VM using “Connect…” started from Failover Clustering, you will need to refresh the VM configuration from Failover Clustering Manager.
6. Multi-select in Cluster Manager
When you select ‘Services and Applications’ or ‘Nodes’ view in the navigation pane of Failover Cluster Manager, the center pane will allow you to select more than one group and take actions. For example, you can select a several VM’s and Turn them all off or Move them to another node. This is very helpful when you are trying to move VMs off of a node in order to perform maintenance on that node.
Of course, don’t forget that if you are using System Center Virtual Machine Manager 2008 R2, you can use the new maintenance mode feature which will automatically coordinate the Live Migration of all VMs off of a single host.
7. Actions for moving VMs in Cluster Manager.
Previously, there were 2 actions exposed for moving a VM in Failover Cluster Manager. Now there are 3:
1. Live Migrate virtual machine to another node: Will initiate live migration of the selected VM. 2. Quick Migrate virtual machine(s) to another node: Will initiate a quick migration of all VMs in the same group. Quick Migration puts the VMs into Saved state before moving them, then resumes them from saved state on the new node.
3. Move virtual machine(s) to another node: Will move the VMs using the Cluster-controlled offline action that is configured in the ‘Settings’ tab of the VM’s properties. Possible Values are Save, Shutdown, Shutdown (forced), and Turn off. The default is ‘Save’, which is effectively the same as a quick migration. If a VM had this setting selected for ‘Shut down’, then the move action will cause the VM to shut down, move, then start on the new node.
Great efforts by Hyper V and Clustering Team here in Microsoft. Just cant praise them enough. Great work guys.. !!!
And all you people who are evaluating Hyper V in Server 2008 R2 RC, go ahead and test these features, its already available to you..
And as always, do leave your comments and feedback..
I leave you with this Hyper V Video.. Have fun and Enjoy !!!!
There is no end of road for Virtualization Team here in Microsoft for coming up with great features in Hyper V.
So what's the BIG NEWS ??
Microsoft Announces following two features now supported on Hyper V R2 which is included in the Windows Server 2008 R2 RC and Hyper V Server 2008 R2 RC released recently.
Very Soon we all be working with 8 Core processors in our servers increasing the Logical processor no. to 64 ( 8 Processors X 8 Cores ). So now Microsoft Hyper V Supports 64 Logical processors, now you can consolidate more Virtual Machines on a single Host.
Hyper V Evolution from 16 Logical Processor Support to 64 Logical Processor Support:
Why do we need Processor Compatibility mode??
The OS and applications within a VM are exposed to the processor features on that server. However, when the VM is quick/live migrated to another server, the destination server may have a processor with a different set of features. An OS or application may try to execute CPU features that it discovered when it was started on source host but may not be present on the destination host - resulting in a failure.
Now You can do the live migration of Virtual Machines from one host to another in a cluster even if the processors features sets are different (But same Family Intel-Intel, AMD-AMD)
So far we need to have identical processors on all the nodes in our cluster for Live Migration to work, but what if other node has different feature processor. Processor Compatibility Mode comes to rescue.
When a VM is started with processor compatibility mode enabled, Hyper-V only exposes guest visible processor features that are available on all Hyper-V enabled processors of the same processor architecture, i.e. AMD or Intel. This allows the VM to be migrated to any hardware platform of the same processor architecture.
Note: You cannot do a Live Migration from Intel to AMD or vice versa. Processor family should be the same. :-)
Note: Processor compatibility mode does not leverage Intel’s FlexMigration or AMD’s AMD-V Extended Migration technologies. Processor compatibility mode has no dependencies on these technologies.
VM’s processor compatibility mode is OFF by default. It can be turned on by one of the two ways:
Using Hyper-V Manager: from Hyper-V Manager, select CPU setting wizard of the VM. Check a check-box labeled “Migrate to physical computer with a different processor version”.
You can change this setting only when VM is not running.
Using System Center Virtual Machine Manager 2008 R2 RC : Releasing SOON
This is just amazing, Hyper V Team is outperforming themselves over and over again. WAY TO GO TEAM!!!!
Let me know your comments and feedback
Service Pack 1 Beta
If you haven't seen it already, Microsoft has released an FAQ document related to Windows 7 and Server 2008 R2 Service Pack 1 BETA
Notable thing here is this one:-
Q. Can I upgrade from the beta builds to the final build of SP1? A. No. You will have to uninstall the Service Pack or do a clean install of Windows 7 or Windows Server 2008 R2.
So there wont be any support for upgrading from Beta to SP1 Final version, so its recommended to run SP1 beta in Test and evaluation environment only and not in production.
Here is the complete FAQ:
Windows 7 and Windows Server 2008 R2 Service Pack 1 Beta Frequently Asked Questions
Q. What is Windows 7 SP1? A. Windows 7 Service Pack 1 is an update for consumers and IT Pros that helps keep your PCs supported, provides ongoing improvement to the operating system, by including previous updates delivered over Windows Update as well as continuing incremental updates to the Windows 7 platform based on customer and partner feedback, and is easy for organization to deploy a single set of updates.
Q: What is Windows Server 2008 R2 SP1? A: Windows Server 2008 R2 SP1 is an update for enterprises and IT Professionals that includes virtualization enhancements, previous improvements delivered via Windows Update, and addresses feedback from customers.
Q. What are the system requirements for the Service Pack 1 beta? A. Your current operating system must be the Release to Manufacturing (RTM) version of Windows 7 or Windows Server 2008 R2 (build 7600).
Q. Can I install the beta on an evaluation version of Windows 7 or Windows Server 2008 R2? A. Yes. The beta of SP1 can install on RTM evaluation versions of Windows 7 and Windows Server 2008 R2.
Q: When will SP1 be released? A: Service Pack 1 will be released within the first half of calendar year 2011.
Q: Who should download and install the Service Pack public beta, when it’s available? A: The public beta is best suited for IT Pros and developers who need to test the service pack in their organization or with the software they are developing. The ISO download for Windows 7 SP1 will contain both 32 and 64 bit versions. The final release of Service Pack 1 will be available through Windows Update for consumers when it is ready.
Q: Should customers who are considering deploying Windows 7 wait for SP1? A: No. Windows 7 is a high quality release and provides many benefits to consumers and businesses alike. SP1 will include all updates previously available to Windows 7 users through Windows Update, so there is no reason to wait or delay their use of Windows 7.
Q. Will there be a slipstream build of SP1 beta? A. No. The beta will only be available as the Service Pack update itself. You will need to have a Release to Manufacturing (RTM) version of Windows 7 or Windows Server 2008 R2 to install the beta of the Service Pack.
Q. What languages will be released at beta? A. For beta, we will release English, French, German, Japanese, and Spanish.
Q. Will I be able to uninstall the service pack beta? A. Yes, you will be able to uninstall the service pack beta if you need to.
Please Note, it is always a best practice to back up your data prior to installing any beta software.
Q. Will the beta stop functioning after a certain amount of time? A. Yes. You will be reminded beginning March 30, 2011. The beta will expire on June 30, 2011. You will have to upgrade to a newer build or uninstall and return to the RTM build by that time.
Q: What other improvements are included in Windows Server 2008 R2 SP1 besides the virtualization enhancements? A: Please see the Notable Changes document for detail on the additional improvements in SP1.
Q: Is RemoteFX different than Remote Desktop Services? How do they integrate? A: RemoteFX describes a set of rich media capabilities that are available to customers using the Remote Desktop Services platform to deploy a virtual machine- or session-based remote desktop infrastructure. Specifically, RemoteFX enhances the Remote Desktop Protocol (RDP) in Remote Desktop Services, so that remote workers can access any type of application or screen content, including rich media and 3D applications, improving end user productivity.
Q: Will Dynamic Memory be available on Microsoft Hyper-V Server 2008 R2? A: Yes.
You can access the online version here
In addition to Windows 7 and Windows Server 2008 R2 RC, Microsoft also announced the public availability of Microsoft Hyper-V Server 2008 R2 RC (the stand-alone Hypervisor based product) this week.
Microsoft Hyper-V Server 2008 R2 RC is a bare metal hyper Visor without the Operating System, and Its FREE download from Microsoft.com
So what are the new features of Hyper V Server 2008 R2?
Microsoft Hyper-V Server 2008 R2 contains the same Virtualization enhancements as in Windows Server 2008 R2 RC.
To name a few:
Configuration Utility (SConfig) and is included with both Microsoft Hyper-V Server 2008 R2 and Windows Server 2008 R2 Server Core.
New configuration options have been added for R2 including:
So how its different from the previous Hyper V Server 2008 and Windows Server 2008 R2?
Here is the chart:-
So go ahead and download the Windows Hyper V Server 2008 R2 RC from here and GET VIRTUAL NOW and do let me know what you think..
From today I’ll be writing a series of posts regarding my experiences with deploying and managing Microsoft System Center Configuration manager in my test lab scenario.
Before I start today, I would like to give a brief description about System Center Configuration Manager and what it does:
Microsoft System Center Configuration Manager 2007 (ConfigMgr) provides a comprehensive solution for change and configuration management for the Microsoft platform, enabling organizations to provide relevant software and updates to users quickly and cost-effectively.
Configuration Manager 2007 provides the following features:
■ Collecting hardware and software inventory.
■ Distributing and installing software applications.
■ Distributing and installing updates to software, for example security fixes.
■ Restricting computers from accessing the network if they do not meet specified requirements, for example having certain security updates installed.
■ Deploying operating systems.
■ Specifying what a desired configuration would be for one or more computers and then monitoring adherence to that configuration.
■ Metering software usage.
■ Remotely controlling computers to provide troubleshooting support.
Please see the following figure to understand where does the SCCM fits into the System Center Solution:
Configuration Manager provides a comprehensive solution for change and configuration management, enabling organizations to provide relevant software and updates to users efficiently. Configuration Manager features provide solutions for many key issues that IT administrators face while managing Windows-based PC environments today.
So now we have a overview of what exactly Configuration manager does and how it helps managing Windows based IT infrastructure, we’ll go into deploying it into my lab.
Beside new year celebration, last weekend was also great as I went out with my friends to watch Avatar. The 3D version is awesome and those you haven't seen the movie yet, go ahead and watch it in 3D.
Its amazing 3D special effects scenes will drive your crazy.
James Cameron has pulled it off spectacularly.
For all who are running Windows 7, You will just love the new AVATAR theme released for Windows 7 from Microsoft
Here is how my desktop looks like :)
Download it here.
For more Windows 7 themes, click here
Its awesome.. isn't it ?
This article is cross posted from my original post on PTS Official Blog
I have been delivering a lot of sessions on the all-new VMM 2012 lately to both external and internal audiences, so I thought of sharing some information with our online community as well.
I am putting together a 3-part series of blog posts to cover all the aspects of VMM 2012 and how it enables Private Cloud Management. If you are new to Private Cloud concepts and its benefits, you may want to read some of my earlier posts on the same topic:
Private Cloud– Part 1
Private Cloud– Part 2
In March at the Microsoft Management Summit 2011 held in Las Vegas, we announced the public availability of VMM 2012 Beta. I know most of you are evaluating VMM 2012 in your environment and may need some guidance—hence this blog series.
When we talk about Private Cloud, we expect following benefits:
1. Reliability and predictability: We would want our application to be highly available and fault-tolerant, the remediation from failure should be simple, and it should be simple to re-start and re-deploy applications.
2. Highly automated: We want our infrastructure to be highly automated to complete tasks like provisioning new systems and configuring storage, networking, and applications on its own without any manual intervention.
3. Agility of speed: We would also expect better responsiveness and turnaround time to meet user needs. We want applications to be deployed faster, and changes to be made much easier and faster—not taking weeks to happen.
4. Focus of Applications and services: Let’s face it, at the end of the day the consumer only cares about applications and services, uptime, and quality of the service as a measure for success of your private cloud. So as a cloud consumer I would want to focus on the application rather than underlying infrastructure.
Today let’s go through a high-level overview of VMM 2012 and what kind of advanced management capabilities it brings to the table to for virtualized infrastructures and the Private Cloud.
Microsoft has made investments in 4 different areas in VMM 2012:
2. Fabric Management
3. Cloud Management: In VMM 2012, a private cloud provides the following benefits:
4. Services Management: It’s not VM Management anymore. Now with VMM you can deploy and manage multi-tier applications across multiple servers as a single unit. Scale out the service with minimal effort based on demand.
We'll discuss some of these great details in my new few blog posts and will also see how to deploy some of these. Stay tuned!
Microsoft Hyper V Server 2008 R2 final release is now available for download and to be deployed in production.
If you are following this blog, we have reviewed every development phase of this product starting from BETA, RC and RTM.
Lets review the differenced between Hyper V Server 2008 and Hyper V Server 2008 R2.
Download it from here
Here is a list of the features in Hyper-V Server 2008 R2
To manage the Hyper V Server 2008 R2 remotely, you need RSAT tool for Windows 7 check my last blog post here how to download and install.
To know more about Microsoft Hyper V Server 2008 R2, Click here
Let me know how it goes. :)
A lot has been said and written about Microsoft Licensing policy related to CALs required to access non Windows Server 2008 VMs on Microsoft Server 2008 Server Hyper – V.
If you move your physical Windows Server 2003 Operating System Environments (OSE) to run as virtual machines hosted by Windows Server 2008 Hyper-V, Can i use my existing server 2003 CALs?
No, as the virtual instance of Server 2003 running on Windows Server 2008 instance you need to have Server 2008 CALs and not server 2003 CALs.
Those who have Microsoft Software Assurance license can upgrade their licenses to Server 2008
Microsoft has changed its licensing policy relating to CALs accessing Virtual Machines on Server 2008 Hyper V.
Windows Server 2008 CALs are no longer required if you are using Windows Server 2008 solely as a virtualization host. The only exception to this is if you are running Windows Server 2008 virtual machines, which would require Windows Server 2008 CALs.
Check these scenarios:
I hope this will ease the adoption of Microsoft Virtualization Solutions for our customers, for more detailed information, please read the updated Volume Licensing Brief.