From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix?
Date: Sat, 19 Jul 2014 09:30:29 +0200 [thread overview]
Message-ID: <53CA1E95.3030006@redhat.com> (raw)
In-Reply-To: <3AFC9677-55B1-4A93-BFCE-3A90FA872D2F@alex.org.uk>
Il 19/07/2014 09:10, Alex Bligh ha scritto:
>>> Looks like your source and destination machines have different
>>> iPXE ROMs. This could be a packaging problem in your distro.
>
> This is Ubuntu 12.04 to Ubuntu 14.04. I think the 14.04 one is
> correct, and don't want to run with a non-standard qemu there.
No, the old one is _always_ the correct one.
The pxe-* ROMs must be 128k, the efi-* ROMs must be 256k. If distros do
not do that, they have a bug (and as you noticed it's not one that they
can easily work around, since now you have different releases with
different ROM sizes for the same machine types).
> Can I use a different ROM (e.g. the old one) with a command line
> option just for the migrated machines? Obviously when they reboot,
> they'l get a hardware change (which is fine).
Yes, "-global foo.romfile" on the destination QEMU. You can just pass
an empty 128k file to the destination since ROM contents are migrated
properly, and hardware will only change when QEMU restarts.
Migration is extremely complex because you have to strike the right
balance between compatibility and maintainability. Whether it works, it
depends on a lot of factors that vary per distro, and the only thing
that can keep it working is a lot of testing.
I don't know of any distro that actively tests migration except RHEL,
SLES. I'm not sure about Debian. Since there is no free-beer SLES,
you'd better switch to CentOS 7 than keeping Ubuntu 14.04.
Paolo
next prev parent reply other threads:[~2014-07-19 7:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 23:33 [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix? Alex Bligh
2014-07-19 5:51 ` Paolo Bonzini
2014-07-19 7:10 ` Alex Bligh
2014-07-19 7:30 ` Paolo Bonzini [this message]
2014-07-19 8:43 ` Alex Bligh
2014-07-19 8:54 ` Peter Maydell
2014-07-19 8:59 ` Alex Bligh
2014-07-19 10:53 ` Paolo Bonzini
2014-07-19 11:37 ` Alex Bligh
2014-07-21 10:22 ` Paolo Bonzini
2014-07-21 13:59 ` Alex Bligh
2014-07-21 14:11 ` Paolo Bonzini
2014-07-21 14:35 ` Alex Bligh
2014-07-21 14:14 ` Paolo Bonzini
2014-07-22 7:11 ` Amit Shah
2014-07-22 9:50 ` Amit Shah
2014-07-22 9:55 ` Paolo Bonzini
2014-07-22 10:22 ` Amit Shah
2014-07-22 10:32 ` Alex Bligh
2014-07-22 10:54 ` Amit Shah
2014-07-22 11:38 ` Alex Bligh
2014-07-22 11:54 ` Amit Shah
2014-07-22 12:12 ` Paolo Bonzini
2014-07-22 12:19 ` Alex Bligh
2014-07-22 12:47 ` Amit Shah
2014-07-22 12:40 ` Amit Shah
2014-07-22 12:15 ` Alex Bligh
2014-07-22 12:44 ` Amit Shah
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=53CA1E95.3030006@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex@alex.org.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).