On Mon, Nov 10, 2008 at 10:24 PM, walt <[EMAIL PROTECTED]> wrote: > walt wrote: >> >> Hi kvm team, >> >> I'm tracking Linus.git, kvm.git, and VirtualBox.svn, among other >> open source projects. I'm finding a conflict between kvm.git and >> VirtualBox.svn over the version of my linux kernel headers... > > Well, I just discovered the --with-patched-kernel flag, which fixes > my compile problem with kvm, so I guess there is no header conflict > after all. I took so long to try that flag because I didn't know > what "don't use external module" means -- and I'm still not sure > what 'external' means. External to what? to the kernel.
One of the options to build kvm is to build the module distributed with kvm-userspace, instead of the kernel version. Before kvm was included in the kernel, you would be either using this external module distributed in the userspace package or patch your kernel. So this is mostly historical. -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
