Skip to main content

Hardware assisted virtualization may change everything!

Server virtualization is a watershed IT technology because it lets a single physical computer run multiple operating systems, vastly increasing rates of CPU use. But server virtualization also is a highly complex process, and many vendors over the years have been stymied in their attempts to create good virtual machine software. VMware, on the other hand, figured out how to build a binary translator that scans the issue of privilege-instructions processors to operating systems and rewrites the ones that can't be virtualized.

Essentially, VMware's early virtualization software tricked the operating system, Gammage says. Earlier processors contain four privilege levels, which create security Relevant Products/Services boundaries -- they're like one-way doors, he says. A process running in Ring 1 had to ask Ring 0 for permission to access objects to which Ring 1 normally wouldn't have access. Under this setup, virtualization software "fools" an operating system into thinking it's running at Ring 0 -- the most privileged ring -- when it's really not.

Hardware-assisted virtualization changes all this by doubling the number of a processor's privilege levels. If the chip Relevant Products/Services has a greater number of privilege levels, modifying the operating system becomes unnecessary, Gammage says.


I think I'll soon write a couple of posts about the future of virtualization and where VMware, Microsoft, Hitachi, IBM, Sun all fit in. This eco-system is evolving heavily, so don't bet on the leading horse, the race has only begun!

Link

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

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!