Skip to main content

VMware needn't worry about Microsoft?

Honestly Gordon, you lost me here. I really don't rate this as an insightful post. Sorry!

Here's what he has to say:

It seems I have a different perception re competition, both in general and specifically re Microsoft. To wit...

1) I consider competition to be good. Healthy competition generates imagination, creativity, and innovation. Consumers benefit from better products at less expensive prices. Of course, and as we each note, the perception by investors of potential shriveling profit margins and thus a possible declining share price is a legitimate concern. Nonetheless, I cling to the notion that Microsoft's entry into the virtualization space will improve VMWare's products. Whether VMWare proves successful at branding its product remains an unknown. Should this come to be, the company's success will endure for more than a mere season or two.


So my quick take on your take:

1. VMware's product is already improved, Microsoft has yet to do something better. We are obviously waiting for a good competitor, but I doubt that it will be the "primary" drive to push VMware to innovate. On the contrary, VMware will have to strenthen everything else besides its product because that is where the danger lies. verdict: lame
2. Please, some reason this
3. Yeah, they carried the glass ball
4. another lamesly reason

Read the post yourself and judge yourself. I see many blogs, including that of ZDnet really chanting gibberish at many occasions, that unspreads this whole virtualization thing, it undoes it all.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...