Skip to main content

Hostworks customers want VMware but nineMSN insists on Microsoft



Obviously customers don't matter, right?

"Let's say you have 10 four-way quadcore hosts for a big site like Big Brother or NineMSN," he said. "To use all the power of the machines, each core counts as a CPU. The downside is you end up with 40 virtual servers, which is hard to manage.

Hostworks thus tends to only use virtualisation on smaller one- and two-way servers for smaller clients or those with low throughput paths.

Hostworks' server consolidation is somewhat unique in that they are deploying virtualisation tools from both VMware and Microsoft.

Most of Hostworks' customers choose VMware, but NineMSN insists on using Microsoft. "The reason we are deploying both is that NineMSN is half-owned by Microsoft," Gauvin said.


Anyways waiting for a product that will be first class when ready for production in 2008 or 2009, is not really smart. Maybe by then we won't be doing virtualization the way we are today.

Read the rest.

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