Microsoft "adjusts" Viridian feature set

Seems like Microsoft is having problems with delivering some of the promised features that were to be present in Viridian (Longhorn Virtualization). Yesterday the following was published by Windows Server Division WebLog:
So we are making the following changes, and postponing these features to a future release of Windows Server virtualization: · No Live migration · No hot-add resources (storage, networking, memory, processor) · Support limit of 16 cores/logical processors (e.g., 2 processor, quad-core systems is 8 cores; or 4 processor, quad-core system is 16 cores)
The lack of initial support for over 16 cores is one thing, but no hot-add of resources and especially no Live Migration was a surprise to me. Perhaps thats why you aren't really allowed to migrate virtual machines to often? Jokes aside, I think this is a somewhat major blow for Viridian and Longhorn, I really did think at least Live Migration would make it into the final product. After all, thats one of the key points with VMWare VI3, and makes management of the host systems much easier and reduces scheduled downtime to a minimum.

Posted by Christian Mohn aka h0bbel

Post metadata


Published May 11, 2007 08:49
5 comments

Tagged with , , , , , , , and 


5 Responses to Microsoft "adjusts" Viridian feature set:

  • There are currently no comments.

5 Pingbacks to Microsoft "adjusts" Viridian feature set:

Leave a Reply


Contact me

Lets talk!
Get in touch