qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] migrating instances from qemu-kvm to qemu
Date: Wed, 19 Mar 2014 17:08:55 +0000	[thread overview]
Message-ID: <20140319170855.GA10575@work-vm> (raw)
In-Reply-To: <20140319161631.GA32205@mail.hallyn.com>

* Serge E. Hallyn (serge@hallyn.com) wrote:

> Although, some people are using newer qemu with '-M pc-1.0'.  So we'd be
> stopping thing from migrating to support the people coming from qemu-kvm.
> Hmm.

What sometimes happens is that you create a VM (lets say with virt-manager)
on an old installation, and it has the XML file for that VM which I think
includes the machine type.   You upgrade your host or copy your VMs over
and so you still use the old machine definition, and hence still have the
-M pc-1.0

Some people have snapshots rather than just disk images taken with particular
versions and they expect those to be reloadable into newer versions.

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2014-03-19 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 15:42 [Qemu-devel] migrating instances from qemu-kvm to qemu Serge E. Hallyn
2014-03-19 15:49 ` Paolo Bonzini
2014-03-19 15:52   ` Serge E. Hallyn
2014-03-19 16:16     ` Serge E. Hallyn
2014-03-19 16:40       ` Paolo Bonzini
2014-03-19 17:08       ` Dr. David Alan Gilbert [this message]
2014-03-19 17:37         ` Serge E. Hallyn
2014-03-19 17:46           ` Dr. David Alan Gilbert
2014-03-19 19:43             ` Paolo Bonzini
2014-03-20  0:18       ` Cole Robinson
2014-03-21 17:00         ` Serge E. Hallyn
2014-03-21 17:22           ` Cole Robinson
2014-03-21 17:24             ` Serge E. Hallyn

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=20140319170855.GA10575@work-vm \
    --to=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).