Skip to main content

Virtualization on the digital highway...

A quick round up on the news from yesterday and today.

VMware Infrastructure 3 was released and was slashdotted too. Cool! So you know what my idea and vision on the future of Virtualization is and what VMware ought to be thinking (I'm sure the guys are).

  • Make it a utility , so pervasive that you don't have to worry on the sales target anymore.
  • Hook up to all collaborative options.
  • Serve VMware virtualization ready Servers and desktops.
  • Help companies really digg the idea of NOT outsourcing but by virtualizing stuff. After all when the tide is going to shift from globalization to localization, you don't wanna be left high and dry
  • Ride the tide
  • Surf and anti-surf the tide



Sometimes a simple introduction always helps focus on the goals. While VirtualIron goes on to explore the clustering side of it. I always favor ideas of trying for free before buying.



More talk on VMware and MS's chess game. But this game is just like Google vs MS.

Here's the deal:

One leads, other follows
One innovates, other acquires
Me balloon, you gas
I'm on a high, you're dry
Me in Lab, you in bathtub
Me code, you erode



Ya digg?

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