Slashdot Mirror
VMware Opens Up API to Partners
mstansberry writes "This week VMware opens up its source code to its x86 partners, calling it the best mix of open-source and proprietary. While the general public won't get a look at the source code, the likes of IBM, HP, Red Hat and others will. Releasing an API is a way for a company to bring more people into the fold and to get more applications integrated within the platform. But from the looks of last quarter's financial reports, VMware doesn't need much help getting people on board."
How does VMWare fit into EMC's strategic interests? I'm surprised that Apple didn't buy VMWare when they had the chance because with the move to x86 hardware, having VMWare part of OS/X would be killer.
I think that VMWare is finding itself in potential trouble because it is not going to be easy to sustain their financial success with the Open Source projects such as QEMU and Xen gaining ground.
I personally think that hypervisors are overhyped (pun fun!), and that the most practical and useful form of "virtualization" is actually separation as is achieved by Solaris Zones, FreeBSD jails and (the most advanced of them all IMO) Linux Vservers. A pretty good article on it here.
Separtion carries nearly zero overhead, simplifies administration because there is one kernel and one filesystem. It allows for simple "entry" into a virtual server from the main server, and there are other subtle advantages that I can't think of right now probably....
Correct me if I'm wrong, but couldn't the better machines from the old mainframe days virtualize themselves? IIRC someone ported Linux to one of the virtual machines and was able to run a crazy number of instances on one set of hardware.
I know this sounds (is?) crazy, but why not open up the architecture of the old mainframes, and base the next generation of PC hardware on those ideas? CPU and memory are cheap now, but those suckers were designed to be robust back when you couldn't solve all problems by making large clusters of faulty machines - they had to work, period. Surely modern PCs could match much of the power of an old mainframe machine, properly designed, and the whole modern desktop OS and apps could just be run on a virtual instance from a PC. This would allow, say, Windows and Linux to coexist, run at the same time, have no issues crop up that software like VMware has to work around, and allow for all sorts of interesting debugging possibilities (how about booting up another VM to debug a wiped out desktop OS, just by pressing a button on the keyboard?)
IIRC x86 has some real issues with virtualization, but if what I have heard is true and x86 is now mostly a layer put on top of more advanced cores in most CPUs perhaps the problem has already been (largely) addressed. Does this makes sense to anyone else - would it be good to have "desktop mainframes"?
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
Actually, that's not true.
IE 6 for Mac was a fully staffed program, and Jimmy Grewal was the program manager. Immediately after the Safari announcement, a decision outside of MacBU was made to kill IE 6 for Mac. Once this was dead, the program manager actually left Microsoft. To repeat: IE 6 for Mac was actually in internal beta, and was a fully staffed project. Right when Safari was announced, it was killed, and it was killed *because* of the Safari announcement.