public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* A question about upgrading versions of kvm and the guest image
@ 2007-12-09  8:34 Mark Ryden
       [not found] ` <dac45060712090034m7f5f0495n4a1ee26445a254b6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Mark Ryden @ 2007-12-09  8:34 UTC (permalink / raw)
  To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

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?

rgs,
Mark

-------------------------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: A question about upgrading versions of kvm and the guest image
       [not found] ` <dac45060712090034m7f5f0495n4a1ee26445a254b6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2007-12-09  8:51   ` Avi Kivity
  0 siblings, 0 replies; 2+ messages in thread
From: Avi Kivity @ 2007-12-09  8:51 UTC (permalink / raw)
  To: Mark Ryden; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-12-09  8:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox