Skip to main content

VMware : So what will Virtualization fetch?



This nice article at SeekingAlpha. A good summary of how to survive as a Billion dollar company

When distributed transactions hit the mainstream, BEA was there. As transactions expanded into JAVA application servers, BEA shifted too. But the underlying technology had been around for a long time, in some cases 20 years, before being broadly adopted. And even BEA stalled out at $1B in revenues. So, is virtualization set to push a company like VMware into a sustained growth market above $1B in revenues? Thanks to the recent S1 filing we can all see that:

# VMware reached $704M in revenues for 2006.
# Its growth trajectory suggests revenue estimates just above $1B for this calendar year.
# Operating expenses grew rapidly last year, up 100% vs. the 80% revenue increase.

Using some simple back of the envelope figures we’re guessing the stock will trade off of a 50c earnings number and could enjoy a 40x P/E multiple. That means a $20 stock drives a $6.6B market capitalization, and if that scenario plays out EMC will have a nice 10x return on investment over just three years. Still, investors should be concerned over what their equity stake is really buying.


Original stuff is here.

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

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op