Skip to main content

KVM may rout out XenSource

KVM emerged out of an Israeli company, Qumranet, last year as lead developer Avi Kivity posted 12,000 lines of code to a Linux kernel mailing list. The Oct. 19 post "came out of nowhere" and was added to the kernel after a review of "just a few months," said Jonathan Corbet, kernel developer and author of the Linux Weather Forecast, a Linux Foundation update on weekly kernel developments, in an interview.

"It looked like it was kernel-ready on day one. It was an exceptional patch in many ways," said Andrew Morton, Linux kernel maintainer and one of Linux Torvalds' top lieutenants. By "patch," Morton means a donation of new code, not a bug fix or repair of existing code.

The kernel developers didn't know Kivity from previous contributions -- he hadn't made any. Nor was there good information available on his company. "I went to the Qumranet Web site. It didn't tell me much," said Morton. Qumranet, a venture capital backed start up, was still in stealth mode at the time.

Morton handed off the code to developers familiar with both virtualization engines and the Linux kernel and they concluded it appeared to be a strong addition.

The Linux kernel in the fall of 2006 had no modules that could take advantage of the new virtualization assists being built into the latestIntel (NSDQ: INTC) and AMD (NYSE: AMD) chips. XenSource's Xen is supported in Novell (NSDQ: NOVL) and Red Hat enterprise distributions but it remains outside the kernel. Adopting KVM would be one way of allowing the kernel to capitalize on chip developments, thought Morton.


Linkk

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