From: Michael Tokarev <mjt@tls.msk.ru>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: sofa5000@lavabit.com, kvm@vger.kernel.org
Subject: Re: upgrade kvm with running vm
Date: Sat, 09 Oct 2010 10:37:32 +0400 [thread overview]
Message-ID: <4CB00DAC.7080308@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTimbBAHgbnTu2-TL-s=0qmgP-Q9FEbpv5bMTm15=@mail.gmail.com>
09.10.2010 03:36, Teck Choon Giam wrote:
> On Fri, Oct 8, 2010 at 2:03 PM, Michael Tokarev <mjt@tls.msk.ru> 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?
[]
>> 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+.
/mjt
next prev parent reply other threads:[~2010-10-09 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 15:43 upgrade kvm with running vm sofa5000
2010-10-08 4:07 ` Teck Choon Giam
2010-10-08 6:03 ` Michael Tokarev
2010-10-08 23:36 ` Teck Choon Giam
2010-10-09 6:37 ` Michael Tokarev [this message]
2010-10-09 14:52 ` Teck Choon Giam
2010-10-09 15:15 ` Teck Choon Giam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB00DAC.7080308@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=giamteckchoon@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=sofa5000@lavabit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox