Advanced

translation

Story: Windows Goes Xen—by ProxyTotal Replies: 0
Author Content
Igor

Aug 26, 2007
9:18 AM EDT 		Microsoft must have judged that relying on an outside source—and a General-Public-Licensed one, at that—for a piece of technology as central as a hypervisor would be too risky or uncomfortable, leading the Redmondians to opt instead to go it alone. translation: We did not have a clue what is and how the 'hypervisor ' works. A couple years ago we bought a company, which made virtualisation software.We integrated it into our products. Unfortunately, it did not work well enough. Then, we started to learn how the 'hypervisor' works by studying XEN source code. We signed with folks from Xen Source an agreement too. At the same time we paid close attention to VMware list of features. Now, we are ready to design our own virtualisation software. Any similarity to the process of how we created MS .NET is just pure coincidence.

----------------------------------- Reminder: MS signed an licensing agreement for Java with Sun. Few years later they (MS) developed .NET and dropped support for Java on MS platform.

Post a reply to this thread:

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post