Skip to main content

Virtualization: Solaris Containers are better?



Paul from ZDnet has some reasons to say why one ought to choose Solaris against other solutions.

Part of the issue here is that the popularity of PC style virtualization responds to issues the Unix community has never had - the pretend professionalism implicit in copying data processing's commitment to partitioning, and the nineties NT manager's learned aversion to trusting NT with more than one application at a time.

Notice that both of these illustrate what happens when people refuse to adapt as reality changes - the cost and memory management issues that drove partitioning and VM in the 1960s were history by the late seventies, and today's Windows servers can easily handle a number of concurrent applications provided that the load process leaves the registery in a consistent state and no more than one hacks it during operations.


Obviously there are some commets that beg to disagree. I liked the one by toadlife

"because you need to pay for the VM licensing and support, and indirectly because the OS/Applications licenses you need to run on the larger memory or multi-processor models most people select as virtualization hosts usually cost more;"

Wrong. VMware ESX does not cost *that* much money, and in the vast majority of cases, the hosts do not require more virtual processors and memory than their physical counterparts. Furthermore, most servers sit around all day doing absolutely nothing, and times when every server needs processor time are rare, unless your setup is unusual. It also shares common memory pages between hosts, so if you are running five copies of Win2k3 on on physical machine, and they all have the same ntoskernel.exe, that kernel will only be loaded once into memory of the physical machine. The result is that a typical Windows server will only take up around 20-50MB of unique memory from the physical server.


Check out toadlife's full response.

I know, I know. Thread virtualization, network is the computer, multi-core processors, cored-threads, X-cores. KVM. openVZ. I'm sure a lot of people are already cringing as they clutch on to their wallets even harder!

Bottom Line: There are a lot of reasons for customers to choose ESX Servers. There are a lot of reasons to experiment a lot of other things in the labs. How a technology like ESX got to the production? Well ask all those customers!

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