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:46:30 +0000 [thread overview]
Message-ID: <20140319174629.GB10575@work-vm> (raw)
In-Reply-To: <20140319173741.GA621@mail.hallyn.com>
* Serge E. Hallyn (serge@hallyn.com) wrote:
> Quoting Dr. David Alan Gilbert (dgilbert@redhat.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
>
> Right, but so long as it is a shutdown vm image, it shouldn't matter to
> this case whether qemu 1.7 uses the old qemu-kvm cirrus vga ram size, or
> the qemu ram size, right?
Right - but they might have kept it as -M pc-1.0 on purpose, so that they
can migrate it back to another machine with an older qemu.
> > Some people have snapshots rather than just disk images taken with particular
> > versions and they expect those to be reloadable into newer versions.
>
> Disk snapshots should be fine right? Live snapshots no, but then
> I didn't they were actually very well supported anyway. In any case,
> they point would remain that if x% of people have snapshots from qemu-kvm,
> and the rest have snapshots created using qemu but older machine types,
> then whether or not we change the values, either way the other x% or
> 100-x % will not be able to restore...
>
> So still it seems the only sure way to handle this would be for qemu
> to say "old vram size != new vram size; so let me resize the vram".
I'd say if the machine type and other config matches they must stay the same,
if the machine type or appropriate config is different you can change stuff.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-03-19 17:46 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
2014-03-19 17:37 ` Serge E. Hallyn
2014-03-19 17:46 ` Dr. David Alan Gilbert [this message]
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=20140319174629.GB10575@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).