Search
Sponsors
| 07 Jun '07 - 18:13 | | news source ~ In-House WSV ('Viridian") part of Windows Server 2008 SP1?
Visitors of the Teched 2007 conference get a sneak preview at Windows Server Virtualization. At the hands-on labs booths, Microsoft is running an early version of WSV - formerly "Viridian" - allow visitors to get an early glimpse of the features. The lab lets you configure a virtual network with 802.1Q support and create a (x64) multi-processor Virtual Machine. While the Hypervisor did not work at my test machine, the lab revealed some details on Microsoft's strategy around WSV. The lab machine was running Windows Server 2008 beta 3, build 6001, but had an extra ID called "Service Pack 1, v.126". One could conclude that this means that Microsoft will be shipping Windows Server Virtualization as part of a service pack. This would also imply that the first service pack would be out within 180 days after Windows Server 2008 RTM's.
My first experiences with WSV were that the MMC was not that responsive (although the machine had 4 Gb RAM and a x64 OS and CPU). I liked the features like the Powershell cmdlets and the 802.1Q support (much like ESX offers). Click on the links below to see some high-resolution screenshots of Windows Server Virtualization.
WSV: MMC snap-in WSV: OS build information WSV: Build information WSV: Hypervisor "missing" WSV: Virtual Network properties WSV: Virtual Machine properties WSV: Powershell
From Steven Bink:
UPDATE: sources tell me Viridian will NOT be part of win2k8 sp1, it is a wrong assumption. Microsoft usually apply this naming convention also if the OS codebase is Vista+SP1.
Internally they don’t do any difference between vista and longhorn codebase.
so SP1 is more likely to refer SP1 for Vista but this doesn’t mean Viridian will come the same time as Vista SP1. Vista SP1 will come when win2k8 RTMs.
So it’s just a reference to actual state of codebase.
Kenneth (URL) - 12 June '07 - 10:02