public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Mark Ryden <markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: A question about upgrading versions of kvm and the guest image
Date: Sun, 09 Dec 2007 10:51:18 +0200	[thread overview]
Message-ID: <475BAC86.9020602@qumranet.com> (raw)
In-Reply-To: <dac45060712090034m7f5f0495n4a1ee26445a254b6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Mark Ryden wrote:
> Hello,
>
> I had build kvm from sources and then installed a
> a guest according to kvm howto using qemu-system-x86_64.
>
> (/usr/local/kvm/bin/qemu-system-x86_64 -hda vdisk.img -cdrom
> /path/to/boot-media.iso \
>    -boot d  -m 384)
>
> The qemu-system-x86_64 utility is built when you build kvm from sources.
>
> It was with kvm-49; now, I think to upgrade to the latest version of
> kvm (kvm-55);
> my question is:
> should I repeat the process of creating the guest image using the
> qemu-system-x86_64?
> Or can I use safely the old vdisk.img guest image ?
>
> And in general: when upgrading from current version of kvm to a newer one -
> can I use the old guest image (which was created with current
> qemu-system-x86_64)?
> Or must the process of creating an image should be repeated with the new
> qemu-system-x86_64 from the new version?
>   

You should be able to run with no problems immediately after upgrading.
If it doesn't work, please report how, what guest you are using and what
is your host cpu version.

There may be a problem if kvm changes its reported cpuid string and the
guest is sensitive to that, but otherwise it should just work.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

      parent reply	other threads:[~2007-12-09  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09  8:34 A question about upgrading versions of kvm and the guest image Mark Ryden
     [not found] ` <dac45060712090034m7f5f0495n4a1ee26445a254b6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-09  8:51   ` Avi Kivity [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=475BAC86.9020602@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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