We have just published a hotfix for Windows Virtual PC that addresses a compatibility problem when trying to install on an AMD Bulldozer system.
You can download it here: http://support.microsoft.com/kb/2519949
Cheers,
Ben
Last month, Microsoft announced the new TV platform for XBox and a long list of content providers that will be bringing their TV and premium content onto XBox. For more detailed information, please check the press release here and here.
As someone from the IIS Media Services team where Smooth Streaming technology was born, I’m proud to announce that the majority of Xbox Live content providers are using Smooth Streaming as their video streaming technology. Also all content partners who are delivering protected premium Smooth Streaming video are using PlayReady DRM for their content protection. Our team not only provided Smooth Streaming server platform (IIS Media Services) but also delivered Smooth Streaming Client SDK to our partners to build their XBox applications upon. Combining the power of XBox platform with the wealth of TV and premium content is going to be a huge win for both consumers and content providers.
After a few years of evolution, Smooth Streaming now goes far beyond the initial scope of Silverlight online streaming. Today you can use Smooth Streaming to reach a variety of different kinds of clients/devices including browsers with Silverlight, XBox, Windows Phone, Apple iOS devices (iPhone/iPad), Windows 8 (in developer preview as of now) and TVs/STBs(Set-top Boxes). For example, Comcast’s popular Xfinity TV app for iPad/iPhone has been running on top of the Smooth Streaming iOS SDK and delivers TV content using Smooth Streaming technology (link). We also provide Smooth Streaming Client Porting Kit which can be used to easily integrate Smooth Streaming functionalities into many kinds of devices including TVs and STBs.
Smooth Streaming is right at the center of this new wave of revolution for TV and premium video delivery. The journey has just begun.
We released a new hotfix for Hyper-V today.
This hotfix addresses an issue where virtual machines may crash (with a STOP 0x000000D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL error) when it is being live migrated. While this problem is relatively hard to encounter – I would encourage anyone who is using live migration to plan to deploy this hotfix in the near future, as you do not want to hit this accidentally.
You can download this fix directly from here: http://support.microsoft.com/kb/2636573
Alternatively, it is also being distributed through Windows Update. Unfortunately it is only available as an optional update though – so you will need to explicitly select to install it on your servers.
Either way, this hotfix does require that you reboot the physical server so you will need to plan the deployment of the fix appropriately for your environment.
Cheers,
Ben
Today we released a fix for to resolve an issue that can lead to guest VM’s crashing after a live migration. This issue only impacted virtual machines that where utilizing virtual SCSI controllers and was only seen under some specific stress conditions however if you have VM’s with SCSI controllers and utilize live migration than I would recommend investigating and installing this hotfix.
http://support.microsoft.com/kb/2636573
Article ID: 2636573 - Last Review: January 10, 2012 - Revision: 1.0
FIX: The guest operating system may crash when you perform a live migration of Hyper-V virtual machines in a Windows Server 2008 R2 environmentSymptoms
In a Windows Server 2008 R2 environment, you perform a live migration of Hyper-V virtual machines. In this scenario, the guest operating system may crash. Additionally, you receive a Stop error message that resembles the following:
STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
To resolve this problem, install this update on the host computer where the Hyper-V virtual machines are located.
Update information To resolve this problem, install this update from Microsoft Windows Update (http://update.microsoft.com) .Download the update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=06c9e6e0-26de-44dc-a2e7-6a87fe0d5e76)
Release Date: January 10, 2012
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 (http://support.microsoft.com/kb/119591/ ) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1).976932 (http://support.microsoft.com/kb/976932/ ) Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information To use the hotfix in this package, you do not have to make any changes to the registry. Restart informationYou must restart the computer after you apply this hotfix.
Taylor Brown
Hyper-V Enterprise Deployment Team
taylorb@microsoft.com
http://blogs.msdn.com/taylorb
My last challenge for getting all of my server virtual machines over to fixed-size virtual hard disks is moving some of my Windows Server 2008 R2 virtual machines. As a reminder, the goal here is to move a virtual machine on a large dynamically expanding virtual hard disk to a smaller fixed-size virtual hard disk. I have used the same technique as I discussed here – but for obvious reasons the process is quite different, as I cannot use any of the GUI tools. Here is the process I followed:
Once this is all complete, and once you have confirmed that the virtual machine is working properly, you can delete the dynamically expanding disk and the backup.
Cheers,
Ben
Yesterday I showed you how to easily convert a dynamically expanding virtual hard disk to a fixed size virtual hard disk. But, how do you do this if you want to keep your fixed size virtual hard disk as small as possible? Well, here is the process that I use for my Windows Server 2008 R2 virtual machines:
Once this is all complete, and once you have confirmed that the virtual machine is working properly, you can delete the dynamically expanding disk and the backup.
Cheers,
Ben
As I discussed yesterday – I have been working on converting my virtual machines from dynamic virtual hard disks to fixed virtual hard disks. There are a couple of ways that you can do this. The easiest way is to just convert the disks using Hyper-V. To do this you need to:
While this process is fairly easy to follow – it has one big drawback. The fixed virtual hard disk will take up the maximum space of the dynamically expanding virtual hard disk. For some of my virtual machines I had created small dynamically virtual hard disks, so this worked well. But for some of them I had created foolishly large dynamically expanding virtual hard disks.
Tomorrow I will document the process that I used for these virtual machines.
Cheers,
Ben
I have had a couple of days off for Christmas, and once the children were happily playing with their new presents, my mind naturally turned to some outstanding server maintenance that I needed to do.
Top of my list was completing the process of switching all of my servers over to fixed virtual hard disks.
There are two reasons why you should use fixed virtual hard disks in production environments:
Given that my servers are only used by me and my family – performance is not a big concern. And for a long time now I have been using dynamically expanding virtual hard disks for all my server virtual machines. But recently I had a big problem. One of my virtual machines started chewing up huge amounts of space. The result was that my Hyper-V server ran out of space and paused all of my virtual machines (to stop any of them from crashing). When this happened I did some emergency space management, but left most of the virtual machines still using dynamic virtual hard disks.
Converting a virtual machine from a dynamic virtual hard disk to a fixed virtual hard disk can be quite tricky. So this week I am going to blog about some of the tips-and-tricks that I have picked up in the process of switching over to fixed virtual hard disks.
Cheers,
Ben