On Sat, Oct 9, 2010 at 2:37 PM, Michael Tokarev <mjt@xxxxxxxxxx> wrote: > 09.10.2010 03:36, Teck Choon Giam wrote: >> On Fri, Oct 8, 2010 at 2:03 PM, Michael Tokarev <mjt@xxxxxxxxxx> wrote: > [] >> I am not sure about userspace wise. In order to use different version >> of qemu-kvm, besides reboot... there is only one method to run >> different version such as upgraded version or downgraded version... is >> to shutdown all VMs and reload the kvm related kernel modules. > > Someone of us two does not understand something. > > Why are you reloading kernel module? It comes with the kernel, > and if you reloading it, you're rebooting the host, no? If yes, > why? I am not rebooting the server or host. From my previous reply I believe I make myself clear that in order to use upgraded or downgraded qemu-kvm version, without rebooting the server (host) the only method is to shutdown all VMs and reload the kvm related modules. If just restart all VMs will not run the upgraded/downgraded version of qemu-kvm without reboot the server (host) or reload kvm related modules. This is from my person test experience with vanilla kernel 2.6.32.x. > > [] >>> Do Not Mess With Kernel Modules (tm). There's no need to. > > It was for a reason I mentioned this. Again: kvm, for quite > some time already, does not come with kernel modules, the > kernel modules comes with your kernel. You need 2.6.28+ > kernel modules to work with any reasonable kvm userspace, > including even kvm-72 from debian lenny. Earlier kernels > are hopeless for kvm, there were too many various problems > exposed by kvm (this includes debian 2.6.26 kernel). > > There's no need to mess with kvm kernel modules. Unless > you want to use some feature that is present only in some > future release (such as vhost-net for example). But for > these, it may be better to really upgrate the kernel to > 2.6.35+. See my above reply about why there is a need to. Thanks. Kindest regards, Giam Teck Choon -- 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
