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: Fri, 08 Oct 2010 10:03:40 +0400 [thread overview]
Message-ID: <4CAEB43C.3030709@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTinsscjyhqn5O9hNBeMokc7XY7x6gFiN8zgrn6c1@mail.gmail.com>
08.10.2010 08:07, Teck Choon Giam wrote:
> On Thu, Oct 7, 2010 at 11:43 PM, <sofa5000@lavabit.com> wrote:
>> hi everybody,
>>
>> is it a problem to update kvm (the kvm package (qemu-kvm on debian) with
>> the package manager) while some vms are turned on? or should i shutdown
>> all vms first?
If you update kvm userspace while some VMs are running, these
VMs will not "pick" the new userspace, they will continue
running by old userspace, until you restart them. It's just
the same as if you upgrade, say, your shell while it's running -
new sessions will use new shell, alrady running will continue
running using old shell.
> From personal experience (install from source), there shouldn't be a
> problem to perform upgrade/update of qemu-kvm without shutting down
> those running VMs. However, in order to use the updated version of
> the qemu-kvm, you will need to unload those loaded kvm-intel or
> kvm-amd and kvm kernel modules. Such unloading of modules will need
> to shutdown all running VMs in order to successfully unload (rmmod)
> those kernel modules. After unloading, you can reload the updated
> version by using modprobe or insmod after you have done depmod.
Do Not Mess With Kernel Modules (tm). There's no need to.
/mjt
next prev parent reply other threads:[~2010-10-08 6:03 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 [this message]
2010-10-08 23:36 ` Teck Choon Giam
2010-10-09 6:37 ` Michael Tokarev
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=4CAEB43C.3030709@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