Home > Virtualization > Patching and/or Updating Hyper-V : Recomendations

Patching and/or Updating Hyper-V : Recomendations

May 25, 2010 Leave a comment Go to comments
 
 Patching and or Updating a Windows 2008/R2/Hyper-V Physical Host requires a close attention to the minimal details.
 Specially in production environment as we are talking not only to Microsoft patch/updates but also Industry products such as Lan cards drivers, Bios, Software Agents, firmwares, it’s important for you to remember that the updates are required only under certain circumstances ( e.g  updating you Network Lan Driver could let you to lose the Virtual Switchs Networks ).
 
Some recomendations :
 
1. Reduce/avoid some updates by using the Core Version. It’s my favorite version and not only because of this reason but also because it uses a lower resources translating in more CPU/memory to the VMs.
 
2. Only download updates that are available on Windows Update, as well those that are available at the Microsoft Download Center and Vendors Websites. NEVER, NEVER use DRIVERS/FIRMWARES from others sources. My recomendation is always go to the Vendor website to get the most updated driver/firmware. Don’t even think about downloading it from others sites/p2p networks. Why ? Simple, it could contain virus/worms and modified code.
 
2. PLAN : You might need a reboot of the Physical Production Host ( If you already implemented Live Migration, nothing to be worried : just move the VMs to another Hyper-V host . If not, it’s time for you to revise your downtime plan )
 
3.  Change the Windows Update Settings to Check for Updates and to let you choose which one is necessary.
 
 

Comprehensive list of Hyper-V R2 updates

 

Knowledge Base Article Name Date Required? File Name Applies to Availability Link

KB974598

“You receive a "Stop 0x0000007E" error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer”‘

10/1/2009

Yes, if you encounter this error and your server uses a “C-state” (lower power state) that is supported by the processor, but is not supported by Hyper-V.

Windows6.1-KB974598-x64.msu

Windows Server 2008 R2

Hotfix

http://go.microsoft.com/fwlink/?LinkId=181559

KB974909

“The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer”

10/21/2009

No.

Windows6.1-KB974909-v2-x64.msu

Windows Server 2008 R2

Hotfix

http://go.microsoft.com/fwlink/?LinkId=183312

KB975354

“A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2”

11/10/2009

Yes, if you are running a backup or restore solution.

Windows6.1-KB975354-v2-x64.msu Windows6.1-KB975354-ia64.msu Windows6.1-KB975354-x86.msu

Windows Server 2008 R2

Hotfix

http://go.microsoft.com/fwlink/?LinkId=179092

KB975530

“Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0x00000101 – CLOCK_WATCHDOG_TIMEOUT"

11/20/2009

Yes, if you are running Hyper-V on the affected hardware.

Windows6.1-KB975530-v3-x64.msu

Windows Server 2008 R2

Download Center, Hotfix

http://go.microsoft.com/fwlink/?LinkId=179091

Advertisement
Categories: Virtualization
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

%d bloggers like this: