From: Cole Robinson <crobinso@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 20:18:56 -0400 [thread overview]
Message-ID: <532A33F0.5050305@redhat.com> (raw)
In-Reply-To: <20140319161631.GA32205@mail.hallyn.com>
On 03/19/2014 12:16 PM, Serge E. Hallyn wrote:
> Quoting Serge E. Hallyn (serge@hallyn.com):
>> Quoting Paolo Bonzini (pbonzini@redhat.com):
>>> Il 19/03/2014 16:42, Serge E. Hallyn ha scritto:
>>>> Hi,
>>>>
>>>> at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321
>>>> it was found that migrating running vms from a machine with
>>>> qemu-kvm to one with qemu, migration fails due to some mismatches.
>>>> The first one we usually hit is
>>>>
>>>> Length mismatch: vga.vram: 1000000 in != 800000
>>>>
>>>> while the second one is network card (and I have not gone beyond
>>>> that).
>>>
>>> This is just a different default. Make sure you specify the right
>>> model on the command line.
>>>
>>>> The vga one can be handled on the command line by
>>>> specifying the -global cirrus-vga.vrammem_mb=8. However that
>>>> doesn't help with a libvirt migration.
>>>
>>> You can patch Ubuntu's QEMU to detect old machine types (pc-1.2 and
>>> earlier) and give cirrus-vga 16MB memory by default. Migration only
>>> works with versioned machine types (or between same-version QEMU),
>>> so it's okay to only do it there.
>>>
>>>> I guess this happens at ram_load() unfortunately - is there any
>>>> good way that this could be detected at incoming migration time
>>>> and the virtual hardware modified as needed for migration to
>>>> continue?
>>>
>>> It cannot, but the destination can be patched to operate correctly
>>> for the old machine types, on the assumption that migration from the
>>> old machine types is always from Ubuntu's qemu-kvm.
>>>
>>> Paolo
>>
>> Ah, thank you, that assumption should be safe and sounds like a
>> great idea.
>
> 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.
>
FWIW, we've carried a patch like this in Fedora 18, 19, and 20:
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20
As you say, it breaks incoming migration from stock qemu.git. But we never
shipped qemu.git prior to F18 (well, not in any timeframe that matters here),
so back compat wasn't a real concern.
For Fedora 21 we are dropping this patch, since there's been enough releases
for the people to transition:
http://blog.wikichoon.com/2013/12/kvm-migration-from-fedora-17-to-fedora.html
- Cole
next prev parent reply other threads:[~2014-03-20 0:19 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
2014-03-19 19:43 ` Paolo Bonzini
2014-03-20 0:18 ` Cole Robinson [this message]
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=532A33F0.5050305@redhat.com \
--to=crobinso@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).