From the KB: A computer is running Windows Server 2008 R2 and has the Hyper-V role installed. This computer has one or more Intel CPUs code-named Nehalem installed. For example, the Nehalem CPU for a server is from Intel Xeon processor 5500 series and for a client is from Intel Core-i processor series. In this scenario, you receive the following Stop error message: 0x00000101 (parameter1, 0000000000000000, parameter3, 000000000000000c) CLOCK_WATCHDOG_TIMEOUT http://support.microsoft.com/kb/975530
I am a sucker for huge posters that have some technical drawings on them. It makes your office look more professional. I just bumped into a new one, that describes the different components of Hyper-V and their architecture. This is but a small snippet: To download the whole poster, click here.
This Solution Accelerator provides instructions and recommendations to help strengthen the security of computers running the Hyper-V role on Windows Server® 2008. It covers three core topics: hardening Hyper-V, delegating virtual machine management, and protecting virtual machines. Download
One of the main advantages in virtualization is having the ability to quickly recover failed systems. By turning a system into a virtual system you are actually turning it into a file that can be used on any system that has Hyper-V installed on it thus enabling quick recovery of a failed system. The main problem is that to be able to backup a VHD file you need to stop the virtual machine. Now obviously, on mission critical systems you can’t stop a system every time you want to back it up. To overcome this issues, you can us the … Continue reading Hyper-V or VHD Backup
Lately, we have been messing around with Hyper-V (by saying we,I actually mean mean myself and the person that won’t tell me his Kazakh name…). The technology itself is very cool, but as always it has it’s quirks. Oddly enough, after we ironed out most of the issues a blog post appeared on the ‘Ask the Core Team’ blog describing the top issues that they have encountered. The post is very useful (and would have been really great a couple of month ago… :)). Click here for the post.
Hyper-V is cool. It’s simple to install and manage yet it has quite a few interesting quirks that need to be worked out, an example of such a quirk is installing it on HP servers that have teaming enabled: http://support.microsoft.com/kb/950792 An additional interesting point that is worth mentioning is that if you would like to manage a Hyper-V server, and access the consoles of the guest operating systems, you should do so by installing RSAT on your desktop or by working at the console of the Hyper-V server itself. If you try connecting by using RDP, you will not be … Continue reading Hyper-V experiences: Physical to Virtual
…Or why is my server stuck at 53% of an update. This one is a real pearl. I was installing Hyper-v on a relatively standard DL360 G5, after installing the role I installed Hyper-V RTM Update (KB950050) and I was asked to restart the system to complete the update. Sounds simple enough,right? Well after the restart I was waiting for the 3rd stage of the update to complete…so the system is counting percents and it stops counting at 53%. After waiting for about half an hour, I decided to cold boot it yielding the same result. A bit frustrated (to … Continue reading Hyper-V and HP Servers
Yesterday,and ahead of time, the final version of Hyper-V was released. You can find product details at the following link. If you would like to download the update for your Windows 2008 system, click here.
There is nothing better then dogfooding to prove that you believe in yourproduct. I stumbled upon a post on the Windows Server Division Blogdescribing the process of moving the microsoft.com website to Hyper-V: http://blogs.technet.com/windowsserver/archive/2008/06/25/microsoft-com-powered-by-hyper-v.aspx