Skip to main content

VMware Server : Poor man's ESX Server?



Well you are not poor by having VMware Server, you just are not ready for the ESX Server yet. Well with that I mean that if you are seriously deploying VMware Server in your test, dev and staging environments (who isn't these days! My wife came to me telling me that her employer is also running VMware, I mean there are high schools experimenting with VMware. Some of them are even onto ESX Servers! Can't divulge anymore names, sorry)then the virtualization bug has bitten you. And its real sweet pain, the kind of pain you experience when you work out in a gym ;)

So, are you a poor man by deploying VMware Server instead of ESX. No way! You just are gearing up for virtualization. That is all. You will obviously taste the fruits of ESX Server , the premium flagship product of VMware. But just get started with the VMware Server. Do it on Windows , do it on Linux. Just do it!

So sometimes you will find it, other times it will find you. You two will meet at some crossroads, thats for sure!

And when you do fall in love , you sing tales like these...

Thanks to the cool networking features in VMWare, all my virtual systems can be on the local network (direct or NAT) or they can be on their very own private network. I can also mount iso images and have them act as a directly connected CDROM, making installs a snap.


See how this blogger discovered freedom!

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

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!