THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

John Paul Cook

Hyper-V undocumented and unsupported features

The official list of supported operating systems, service packs, and numbers of virtual processors can be found here: http://support.microsoft.com/kb/954958/en-us. If you are willing to venture into unsupported territory, you might find some surprises. I have both 32 and 64 bit Windows 2003 R2 Service Pack 2 virtual machines running with four virtual processors. The same is true of Vista Service Pack 1.

Also of interest is what happens with PAE. Hyper-V requires that hardware Data Execution Prevention (DEP) be enabled in the BIOS. Intel calls this hardware feature the execute disable (XD) bit. AMD calls it no-execute page protection (NX). When DEP is enabled, Windows automatically enables Physical Address Extension (PAE) without having /PAE in the boot.ini. Because of this, your 32 bit guests will work with large ram as the screen captures show. For more information, see http://support.microsoft.com/kb/875352.

PAE

Published Monday, July 07, 2008 10:46 PM by John Paul Cook

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Roy said:

John:

I found a post in a a forum where you (I assume) indicated that you were running Virtual Server 2005 within a Virtual Machine under Hyper-V.

I would like to know more about that expierence.

Thanks

August 18, 2008 10:08 AM
 

John Paul Cook said:

Yes, that probably is my post. I consider running Virtual Server on a Hyper-V virtual machine as a last resort option. It's fine for demos and training purposes. Ideally you want to move from Virtual Server or Virtual PC to Hyper-V.

Ironically, the migration can be easier if you do have Virtual Server running in a Hyper-V virtual machine. You don't want to install Virtual Server on your Hyper-V machine, but it's quite handy to have a Virtual Server available. You can run that instance of Virtual Server from a Hyper-V virtual machine. I recommend that before migrating a virtual machine from Virtual Server to Hyper-V, you should apply all required service packs first. In other words, apply the service packs required by Hyper-V while you are still running on Virtual Server. The reason is that the mouse won't work and you can't install Integration Services until the service pack is installed. It's much easier to get the service pack installed when you have mouse control, which is in the Virtual Server environment. Also, I recommend uninstalling Virtual Machine Additions as the very last step when you are still in Virtual Server.

October 18, 2008 11:10 AM

Leave a Comment

(required) 
(required) 
Submit

About John Paul Cook

John Paul Cook is a Technology Solutions Professional for Microsoft's data platform and works out of Microsoft's Houston office. Prior to joining Microsoft, he was a Microsoft SQL Server MVP. He is experienced in Microsoft SQL Server and Oracle database application design, development, and implementation. He has spoken at many conferences including Microsoft TechEd and the SQL PASS Summit. He has worked in oil and gas, financial, manufacturing, and healthcare industries. John is also a Registered Nurse who graduated from Vanderbilt University with a Master of Science in Nursing Informatics and is an active member of the Sigma Theta Tau nursing honor society. He volunteers as a nurse at safety net clinics. Contributing author to SQL Server MVP Deep Dives and SQL Server MVP Deep Dives Volume 2. Opinions expressed in John's blog are strictly his own and do not represent Microsoft in any way.

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement