Skip to main content

VMware GSX not really meant for production? Sure it is!



I think this news is kind of confusing or atleast talks about a bit of confusion. Anyways as new customers and existing customers, my advice will be

  • VMware's GSX server is a great product, it's just getting free. It still remains a good solid product.
  • GSX (and then the later renamed Virtual Server) will remain for a lot of purposes like QA, Development, Testing.
  • ESX is superior than GSX as it runs closer on the bare metal, so if you expect better (or near HW ) performance, you know what to go for.
  • Sure Microsoft and Xensource are trying to catch up but to you your good and healthy GSX server in production is your concern. And moving to ESX from here is a recommended path anyways (I'd advice it even if VMware's GSX server wasn't being freed)
  • Don't forget that you have a World class virtualization product in house, no other product can replace it.
  • Please don't let any FUD bother you. If you didn't have it , it wasn't yours either.
  • Even if you continue to use the GSX, you'll have full support so don't worry!

Cheers and Virtualize right now!!!

Tarry

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