Skip to main content

Linux is a bare metal Hypervisor!

Kevin Lawton, a friend and one of the pioneers on x86 Virtualization, has finally launched his blog and he starts elegantly with:

here's been a lot of talk about bare-metal hypervisors in the virtualization realm. All academic arguments aside, the reality is that Linux + KVM is a bare-metal hypervisor. You can create a small Linux+KVM image, embed it in a computer like firmware, and add all the same end-to-end attestation that you can with any other software stack. The fact that KVM is a kernel module doesn't change much other than how someone might draw boxes in a powerpoint presentation.

Most of the proponents of Xen based virtualization talk ad nauseum about the attack surface size of a bare-metal hypervisor. Well, then what do you about the monumentally big efforts of creating drivers for all the varied hardware out there, especially on the endpoint? Why you take Linux and ram it into Xen as a control OS. What about the OS features which Linux has grown 17 years to do? Unfortunately, you need to train Xen to handle those -- things like the NUMA model, scheduling, memory management, power management, etc. These are no small feats on notebooks, for example, where hardware variability is high and power management features are critical.

And if you want to get a handle on how fast the feature velocity of Linux is to see what Xen is up against, check out Greg Kroah-Hartman's talk. Greg also comments on KVM, at 40:53 and 45:08.

Kevin's fresh new blog is here!

Welcome to Blogosphere, Kevin!
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