From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH edk2-firmware v2] update to edk2-stable202308
Date: Thu, 31 Aug 2023 15:28:03 +0200 [thread overview]
Message-ID: <6434912e-9b66-459e-c49b-634c401ca7af@proxmox.com> (raw)
In-Reply-To: <4ec3e6ba-3d2d-7bc8-ccaa-344f3b778d69@proxmox.com>
Am 31.08.23 um 14:47 schrieb Stefan Hanreich:
> On 8/31/23 14:39, Thomas Lamprecht wrote:
>> Am 30/08/2023 um 17:50 schrieb Stefan Hanreich:
>>> * Removed 0001-OvmfPkg-PlatformInitLib-limit-phys-bits-to-46.patch
>>> since it has been included upstream since commit c1e85376 [1].
>>>
>>> * Updated the patch
>>> Revert-ArmVirtPkg-make-EFI_LOADER_DATA-non-executabl so it applies
>>> again.
>>>
>>> * had to increase FD_SIZE to 4M for the x64 build as otherwise the
>>> package wouldn't build due to the size of the resulting image
>>
>> I mean new versions are great and what not, but is there a reason why you
>> send this update now? Maybe fix some issue our users face? If so, it'd be
>> great if you could record that here.
>>
>
> I've been trying to reproduce an issue one of our users is facing and
> wanted to check whether newer firmware versions trigger the issue as
> well. Currently, this issue seems fixed with the newer firmware although
> it's hard to say since there is no definite reproducer.
To be a bit more precise, it's an issue were a RHEL VM with 4.x kernel
gets stuck after guest reboot, as far as we can tell right after OVMF
initialization. Mira and Stefan were able to reproduce the issue
semi-regularly with a bunch of VMs rebooting periodically. And Stefan
said it didn't yet trigger with the updated edk2 package for a few days
now. We can't be sure, as it is a race after all, but it does sound
promising.
prev parent reply other threads:[~2023-08-31 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 15:50 Stefan Hanreich
2023-08-31 12:39 ` Thomas Lamprecht
2023-08-31 12:47 ` Stefan Hanreich
2023-08-31 13:28 ` Fiona Ebner [this message]
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=6434912e-9b66-459e-c49b-634c401ca7af@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
--cc=t.lamprecht@proxmox.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