UPDATE: David’s blog posting and images are now gone. My Spanish is not very good, but I don’t see an explanation on his blog.
It’s been 2 months since I last posted about WSV. Still not much happening. The first public beta of WSV has been pushed back to the 2nd half of 2007, but that has been widely publicized.
Today i ran into this translated article by David Cervigón, a Microsoft evangelist. It reveals a little bit of information that I had not known before, along with some screenshots. The original article is in Spanish.
Here is a list things that I thought were interesting.
* Remote console connection via RDP
* VLAN tagging support and vSwitches.
Still no talk of vMotion like support. This is a feature that I consider a requirement to compete with VMware. I have heard rumors of the plans here, but nothing that MS has announced so I will leave it alone for now.
jeremy WSV
It’s the first snow day in a long time here in Minnesota, so I have some free time in between snow blowing and shoveling. I honestly haven’t been following Microsoft’s virtualization offerings in a while. It’s time to see what they are up to.
To make it clear where I stand, by offerings I mean future products. Virtual Server is out there and is a competitor to VMware server (GSX). I’m more interested in something that can compete on a larger enterprise scale. I am interested in the details of Windows Server Virtualization (WSV), codename Viridian. In general, my bare minimum requirements for a product to compete with VI3 are the ability to move VM’s between hosts while online (vMotion).
This all started when I ran into this video today. The video shows hot adding a nic to a VM.
http://blogs.technet.com/aralves/archive/2007/02/28/longhorn-hypervisor-demo.aspx
So first, what is the status of WSV/Viridian? When can I run the beta?
I give up. I read somewhere that a private beta released end of 2006. I would assume we can see some bits following the release of Longhorn beta 3.
So, the following pieces make up Microsoft’s new virtualization initiative.
So far, the details are few. Some standard things, such as
- 8 vCPUs
- Hot add different devices
These things are good, but I am curious about a couple critical points.
- Price. How will this be licensed?
- Shared filesystems (VMFS). How do I vMotion without VMFS?
- Networking. How do they accomplish the equivalent of vSwitches and port groups.
I will follow up as I uncover details.
jeremy WSV