public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "wuchenye1995 <wuchenye1995@gmail.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] A problem with live migration of UEFI virtual machines
Date: Mon, 10 Feb 2020 12:20:59 -0800	[thread overview]
Message-ID: <12553.1581366059422195003@groups.io> (raw)
In-Reply-To: <tencent_F1295F826E46EDFF3D77812B@qq.com>

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

(Replying through the groups.io web interface, just this one time)

wuchenye1995 wrote:

> Hi all,
>
> We found a problem with live migration of UEFI virtual machines due to
> size of OVMF.fd changes.
>
> Specifically, the size of OVMF.fd in edk with low version such as
> edk-2.0-25 is 2MB while the size of it in higher version such as
> edk-2.0-30 is 4MB.
>
> 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.

You can't solve it. The 2MB and 4MB builds of OVMF are fundamentally
incompatible with each other. It's actually beneficial that QEMU cleanly
prevents such attempts at migration; otherwise you'd see misbehavior
that would be much less graceful.

Please see commit b24fca05751f ("OvmfPkg: introduce 4MB flash image
(mainly) for Windows HCK", 2017-05-05) for more info:

https://github.com/tianocore/edk2/commit/b24fca05751f

This is the reason why the Fedora edk2 package build script (= RPM spec
file) uses "-D FD_SIZE_2MB" explicitly.

Thanks
Laszlo

[-- Attachment #2: Type: text/html, Size: 1512 bytes --]

  reply	other threads:[~2020-02-10 20:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10  4:39 A problem with live migration of UEFI virtual machines wuchenye1995
2020-02-10 20:20 ` Laszlo Ersek [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-25 17:53     ` [edk2-devel] " Laszlo Ersek
2020-02-25 18:56       ` Andrew Fish
2020-02-25 20:40         ` Laszlo Ersek
2020-02-25 21:35           ` Andrew Fish
2020-02-26  9:42             ` Laszlo Ersek
2020-02-28  3:20               ` Zhoujian (jay)
2020-02-28 11:29                 ` Laszlo Ersek
2020-02-28  4:04               ` Andrew Fish
2020-02-28 11:47                 ` Laszlo Ersek
2020-02-28 11:50                   ` Laszlo Ersek
2020-03-02 12:32               ` Dr. David Alan Gilbert

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-list 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=12553.1581366059422195003@groups.io \
    --to=devel@edk2.groups.io \
    /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