Skip to main content

Virtualization and pricing: Price per VM wars

Microsoft's story

James goes on price/VM:

Who's cheapest now ?

Now if the customer is prepared to $5,750 (plus support, training, and extra management tools) on VI3 enterprise... what would they get if they spent that on RAM


VMware VI3 enterprise Free Hypervisor
Total Cost $17,748 $17,748
Windows Licences $5998 $5998
Virtualization licences $5750 $0
2 way Server, $6000 $6000
RAM 4GB 32GB
VMs 14 (with 2x overcommit) 63
Price per VM $1268 $281

Who's cheapest now ? Oh look it's Microsoft again.



read rest here.



Citrix's response on what VDI is and what it is not

and

VMware's blog where Petrillo does some talking again.

Funny thing though here, Mike. I'd never push this client into some blog controversy. We too are doing big and small VDI deployments provided by several virtualization vendors. Bringing a customer's data into play would mean one very simple thing: what if your competitors get to them and show them that they can do it better (depending on the version of what is "better")

There has been a lot of talk on this blog and others about memory overcommit. Several of the blogs have tried to discredit the power of memory overcommit by saying it's never used by customers in the real world and can simply be overcome by adding more memory to the server (see the long discussions in previous posts on this blog). One VMware customer has already commented about how he architects his environment with memory overcommit in mind. I received a private response from another VMware customer who is getting ready to implement a very large VDI environment with some interesting numbers that I'll walk through below. The customer is a large US bank and to protect the security of their environment I did black out some of the names in the screenshots.
I'd be pissed off if I were the sales guy who managed to get that customer!
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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...
Post a Comment
Read more