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.
Post metadata
Published May 11, 2007 08:49
5 comments
Tagged with computing, hypervisor, longhorn, microsoft, vi3, viridian, virtualization, VMWare and windows
5 Responses to Microsoft "adjusts" Viridian feature set:
5 Pingbacks to Microsoft "adjusts" Viridian feature set:
May 11, 2007 9:21am
[…] Microsoft “adjusts” Viridian feature set […]
May 11, 2007 9:22am
[…] некоторых блогах уже появились предположения что это решение может быть связано с нежеланием Microsoft […]
May 12, 2007 12:26am
try to avoid schadenfreude in this blog, so I’ll just point to this VMTN Forum thread since Fred points out the ability to do a “live migration” (vMotion), is really a baseline requirement for an enterprise virtualization solution. See also Scott Lowe, h0bbel, baeke. Virtualization More Powerful Than Ever: “From virtual SANs to virtual PCs and right down to such esoteric matters as disaster recovery and business continuity, it turns out that the virtual environments being installed now have the
May 14, 2007 10:25pm
[…] to many are the postponement of live migration and hot adds of resources. Bloggers Scott Lowe and h0bbel (aka Christian Mohn) point out that live migration presents the bigger competitive loss for […]
July 24, 2007 5:41am
[…] migration functionality really is, in my opinion, a serious stumbling block for Microsoft. I wasn’t the only one that thought so, either. (There was a post about it on the VMTN Blog at some point as well, […]
Leave a Reply