I recently blogged about PowerShell + VMWare. I have also taken a look at the PowerShell management offering around Hyper-V. Hyper-V places WMI as the primary management interface. That makes perfect sense as the lowest common, standards based, denominator. This interface is then abstracted via PowerShell which frankly will be where most people will choose to work.
I was however quite surprised to see that Microsoft have chosen to make this an open source project. Would it have been better to provide a supported solution and then supported a "PowerShell Hyper-V Lib" project on codeplex or a "PowerShell Hyper-V Community Extensions project"? For example: SQL Server 2008 PowerShell is part of the SQL Server 2008 installation - admittedly they don't ship many cmdlets. The Exchange Management Shell based on PowerShell is probably the best example of PowerShell support being shipped by Microsoft.
I really think Microsoft should consider shipping thorough PowerShell support for all their server platforms to support the ITPros and MSBuild tasks to support the developers. Any more-than-trivial server deployment requires scripting, and any more-than-trivial software development requires a good build. Not shipping a rich PowerShell or MSBuild suite with their products seems to be failing to recognise how their customers are using their products which would seem extraordinary given that they manage a fairly impressive infrastructure of their own and they are the largest software development company in the world!