diff options
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/2234.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/2234.toml | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2234.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2234.toml new file mode 100644 index 000000000..ecc6ea7e9 --- /dev/null +++ b/gitlab/issues/target_missing/host_missing/accel_missing/2234.toml @@ -0,0 +1,31 @@ +id = 2234 +title = "upon pressing F2 failures in loading the edk2 bios interface app" +state = "opened" +created_at = "2024-03-21T07:36:03.391Z" +closed_at = "n/a" +labels = ["GUI"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2234" +host-os = "Windows 10" +host-arch = "x86_64" +qemu-version = "QEMU emulator version 8.2.90 (v9.0.0-rc0-42-g54294b23e1)" +guest-os = "NA just the uefi tianocore edk2 bios" +guest-arch = "x86_64" +description = """Cosmetic, low priority, but maybe easy to fix +Occasional failures to load the edk2 bios interface app +Workaround, retry until success""" +reproduce = """1. start qemu +2. press F2 when qemu guest display window pops up. When it works, it brings up the edk2 bios interface. + This bug concerns the case when it does not work + +For reasons not clear, sometimes, after pressing F2, and after qemu registered the key-stroke (F2) and responded by changing the window size, the bios interface loading process seems to abruptly stop at the following guest-display-screen with the following message. +```BdsDxe: Loading Boot0000 "UiApp" From Fv(7CB8BDC9-F8EB-F434-AAEA-3EE4AF6516A1)/FvFile(462CAA21-7614-4503-836E-8AB6F4662311)``` + + +When the bios interface loading process does succeed, it goes to the expected screen: +""" +additional = """Unsure if this sort of bug should go upstream to https://github.com/tianocore/edk2/issues +Herein notifying @kraxel + +Not a measured statistic, but on basis of feeling, I'd qualitatively say 4 out of 5 times it fails to bring up the bios interface. Its a bit frustrating because it feels like one has no control over it and a successful event is left to chance. + +This isn't a recent introduction/regression. I've noticed this since 8.0.0, so its been this way maybe longer.""" |