VirtualBox 6.0 and rEFInd 0.11.4 icons missing due to inaccessible files on ISO9660 partition

[nickel]

When running a VirtualBox virtual machine using LiveCD with rEFInd boot manager utility (doesn't matter if it is an official refind_cd_0.11.4.iso or a custom Linux distribution using rEFInd as a boot manager) icon missing bug occurs. VirtualBox 6.0 affected as previously 5.x.xx were (https://www.virtualbox.org/ticket/18039).

Host systems: Alt Linux KWorkstation 8.2, Ubuntu Studio 16.04 Guest systems: Alt Linux KWorkstation 8.2 LiveCD, refind-cd-0.11.4.iso

Description: In case of refind-cd-0.11.4.iso the bug is easily reproducible and has a "triggering" symptom: for the first time boot occurs some icons are missing and replaced with black-yellow striped squares). After timeout is hit and "Boot Fallback" bootloader is run rEFInd rescans bootloaders and ALL icons appear on screen. Then one more rescan triggered by running "Boot Fallback" bootloader will make them disappear and this may long ad infinitum.

How to reproduce:

Install VirtualBox 6.0 for Linux; Create a linux machine with EFI;

"load" refind-cd-0.11.4.iso ​https://sourceforge.net/projects/refind/files/0.11.4/refind-cd-0.11.4.zip/download as an only boot media Run the machine Wait until reEFInd timeout is hit with "Boot Fallback bootloader" option selected or run it manually

Result: triggering appearance/disappearance of some boot options'/tools' icons

As it was mentioned in rEFInd discussion thread ​https://sourceforge.net/p/refind/discussion/general/thread/f9f2c6ec68/ the most probable reason for described issue is EFI ISO-9660 filesystem driver code.

It turns out that image files are listed as existing by "ls" command in EFIShell("no files found" report on such partitions on real hardware and QEMU/KVM), but report "access denied" when "edit" command issued upon them.

PS: this bug CANNOT BE reproduced using real hardware and QEMU/KVM virtual machine.

-- Best regards, Nikolai Kostrigin ALT Linux Team

[Socratis]

A blatant duplicate of #18039.

• You don't have to open a new ticket for every VirtualBox version.
• You don't have to characterize cosmetic bugs as "Critical", then "critical" loses its meaning...

[janitor]

#18039