On 03/21/2010 01:21 PM, Thomas Løcke wrote:
Hey all, I've recently started testing KVM as a possible virtualization solution for a bunch of servers, and so far things are going pretty well. My OS of choice is Slackware, and I usually just go with whatever kernel Slackware comes with. But with KVM I feel I might need to pay a bit more attention to that part of Slackware, as it appears to a be a project in rapid development, so my questions concern how best to track and keep KVM up-to-date? Currently I upgrade to the latest stable kernel almost as soon as its been released by Linus, and I track qemu-kvm using this Git repository: git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git But should I perhaps also track the KVM modules, and if so, from where? Any and all suggestions to keeping a healthy and stable KVM setup running is more than welcome.
Tracking git repositories and stable setups are mutually exclusive. If you are interested in something stable I recommend staying with the distribution provided setup (and picking a distribution that has an emphasis on kvm). If you want to track upstream, use qemu-kvm-0.12.x stable releases and kernel.org 2.6.x.y stable releases. If you want to track git repositories, use qemu-kvm.git and kvm.git for the kernel and kvm.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
