From: Thomas Mueller <thomas@chaschperli.ch>
To: kvm@vger.kernel.org
Subject: Re: About upgrade KVM
Date: Thu, 27 May 2010 08:32:31 +0000 (UTC) [thread overview]
Message-ID: <htlamv$70g$1@dough.gmane.org> (raw)
In-Reply-To: 20100527152458.5b5q33mccggk4ssc@oswebmail2.pacific.net.hk
>
>
> On marking them to install following warning popup:- Mark additional
> required changes?
>
> To be removed
> kvm
>
> To be added
> libasyncns0
> libcap1
> libpulse0
> - end -
>
>
> My questions are;
>
> 1)
> On deleting the old package whether it would affect the running virtual
> machine?
IMHO they won't be affected until "shutdown" of the guest and/or the host.
>
> 2)
> Is there any way to come back in case of problem?
backup the old kvm package (look in /var/cache/apt/archive) before
upgrade.
beaware that some command line switches changed between 0.9.1 and 0.12.4.
and upgrade your host kernel too (2.6.32 is in backports) for a newer
version of the kvm kernel module (don't know if kvm-72 works with 0.12.4)
- Thomas
prev parent reply other threads:[~2010-05-27 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 7:24 About upgrade KVM satimis
2010-05-27 8:32 ` Thomas Mueller [this message]
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='htlamv$70g$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=kvm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).