From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: wuchenye1995 <wuchenye1995@gmail.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
edk2-devel <edk2-devel@lists.01.org>,
zhoujianjay <zhoujianjay@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: A problem with live migration of UEFI virtual machines
Date: Thu, 20 Feb 2020 15:47:43 +0000 [thread overview]
Message-ID: <20200220154742.GC2882@work-vm> (raw)
In-Reply-To: <tencent_3CD8845EC159F0161725898B@qq.com>
* wuchenye1995 (wuchenye1995@gmail.com) wrote:
> We found a problem with live migration of UEFI virtual machines due to size of OVMF.fd changes.</div><div class=" selfdiv" style="height: 79.6875px; width: auto !important;"
> Specifically, the size of OVMF.fd in edk with low version such as edk-2.0-25 is <b>2MB</b> while the size of it in higher version such as edk-2.0-30 is <b>4MB</b>.
> When we migrate a UEFI virtual machine from the host with low version of edk2 to the host with higher one, qemu component will report an error in function
> qemu_ram_resize while
>checking size of ovmf_pcbios: Length mismatch: pc.bios: 0x200000 in != 0x400000: Invalid argument.
>We want to know how to solve this problem after updating the version of edk2.
When you migrate, you must migrate between identical configurations; so
you need ROM images (including edk2) that are the same size.
There's two answers;
a) Stick with the same version of the ROM between VMs you want to
migrate
b) Pad your ROM images to some larger size (e.g. 8MB) so that
even if they grow a little bigger then you don't hit the problem.
Dave
P.S. Please use plain text email
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-02-20 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 8:53 A problem with live migration of UEFI virtual machines wuchenye1995
2020-02-20 15:47 ` Dr. David Alan Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-11 17:06 wuchenye1995
2020-02-11 17:39 ` Alex Bennée
2020-02-24 15:28 ` Daniel P. Berrangé
2020-02-10 4:39 wuchenye1995
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=20200220154742.GC2882@work-vm \
--to=dgilbert@redhat.com \
--cc=devel@edk2.groups.io \
--cc=edk2-devel@lists.01.org \
--cc=qemu-devel@nongnu.org \
--cc=wuchenye1995@gmail.com \
--cc=zhoujianjay@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.