On Saturday, May 29, 2010, Sean Dague wrote: ... > To be fair, all of the approaches require kernel modules. The kvm > ones are open source and upstream, the others aren't.
The VirtualBox kernel module sources are open source as well (I'm building them when I make custom kernels) -- it's just harder to tell they're open because the VirtualBox sources use a mixture of licenses: GPLv2, MPL, BSD, LGPL v2.1. Some files are dual-licensed and also covered under CDDL. > Because they all use kernel modules to assist various parts of > virtualization, they are typically mutually exclusive on a single > box. The fact that kvm is tested as part of the distro, helps > eliminate bugs. Likewise because the VirtualBox modules haven't been incorporated upstream into the Linux kernel itself, on at least one occasion I've run into an issue where Linux kernel changes caused some minor VirtualBox breakage (bridged networking). -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 2 - Android Jul 7 - Patent Absurdity - The Movie Aug 4 - Samba
