Most Popular
| Top Stories | Commented | Featured |
Weekend Open Forum: Have you upgraded to Windows 7 yet? What is there to like/not? featured
Tech Tip of The Week: Turn Off your Display Using a Windows Shortcut and More featured
Netflix PS3 streaming arrives tomorrow
Dell's ultra-thin Adamo XPS to ship soon for $1,799
Windows 7 crushed Vista in early launch sales
Nvidia Tegra 2 to double performance, arrive next year?
TS Community
| User Gallery | Recent Discussion |
 My 2001 Dodge Ram 1500 4x4 by cascott |  COBOL stay away from it! by Julio |
 Raggy Case by Jaf |  TechSpot at CES 2007 by Julio |
TechSpot RSSInformation Technology
Microsoft to delay Virtual Server beta release
Viridian, Micrsoft's answer to VMWare and virtualization in general, has been hit by a few setbacks. The Beta, originally schedule for a release in the first half of this year, won't come until the second half. It seems certain features Microsoft wanted to include are causing issues with performance and scalability that warrant it being pushed back:
Microsoft wanted to add in things such as support for 64 processors – "something no other vendor's product supports" – and on-the-fly addition of processors, memory, disk and networking. Such technology was needed so that Microsoft could "(meet) our internal goals for performance and scalability."
It's better to be late than to be broken, and better to be safe than sorry. Given that virtualization is intended for businesses and enterprise platforms, Microsoft really should be aiming for a flawless launch. A delay is not surprising. Some, however, are criticizing their overall plan to enter the market to begin with, calling Viridian flawed from the getgo:
"Microsoft has a fundamentally broken server virtualization strategy at this point," wrote Illuminata analyst Gordon Haff. "They were behind to begin with. Now, the tardy 'Rev. 1.0' is starting to look more like 'Rev. 0.5.' Perhaps it’s time for Microsoft to consider a different angle.
They are calling for MS to enter into partnerships with other companies, rather than try and do it themselves. A bit late for that, though, with all that they have invested into Viridian.
Microsoft wanted to add in things such as support for 64 processors – "something no other vendor's product supports" – and on-the-fly addition of processors, memory, disk and networking. Such technology was needed so that Microsoft could "(meet) our internal goals for performance and scalability."
It's better to be late than to be broken, and better to be safe than sorry. Given that virtualization is intended for businesses and enterprise platforms, Microsoft really should be aiming for a flawless launch. A delay is not surprising. Some, however, are criticizing their overall plan to enter the market to begin with, calling Viridian flawed from the getgo:
"Microsoft has a fundamentally broken server virtualization strategy at this point," wrote Illuminata analyst Gordon Haff. "They were behind to begin with. Now, the tardy 'Rev. 1.0' is starting to look more like 'Rev. 0.5.' Perhaps it’s time for Microsoft to consider a different angle.
They are calling for MS to enter into partnerships with other companies, rather than try and do it themselves. A bit late for that, though, with all that they have invested into Viridian.
Related Stories
