Skip to main content

Virtualization drag



This article walks through several scenarios and yet another attempt to warn users. Why they used the title "VMware: the..." is something I can't comprehend. In many ways this article is repetetive.

Oddly enough, then, when we recently asked readers which tech buzzword they most despise, virtualization came in a strong second, just behind SOA. One in four respondents threatened bodily harm to the next salesperson who mentioned it, and 20 percent said they didn't realize expected benefits.

Still, virtualization is here to stay, and that's a good thing despite its apparent image problem. Whether you use Microsoft Virtual Server, VMware, Xen or another package, virtualization delivers a raft of benefits, from better use of physical assets to improved management of applications to the ability to divvy up resources across machines in a way that the sum of a virtual assigned resource--such as memory--exceeds actual physical memory. Using virtual machines may reduce physical server count by moving older applications off older hardware to newer systems that are less likely to experience hardware failure or, in the event of failure, have better parts availability. We found ways to boost the payoff from virtualization technologies, and our testing highlights which areas will suffer least from performance drags.


Since VMware's ESX is under spotlight everytime someone wants to talk about virtualization. A lot of people are indeed getting a bit tired with the "overuse" of the term Virtualization.

You ought to talk to the clients who have used VMware VI3 successfully in their environments. Go to VMworld this year and see and hear how they have squeezed all the servers without compromising on performance. Read the rest of the article 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