VM not started after updating guestaddition from 5.1.22 to 5.1.26

[yasu]

Hello expert,

I need your help.
When I update the guestaddition to 5.1.26 from 5.1.22, the following message appeared on VM display, and could not start Linux OS.

UEFI Interactive Shell v2.1
EDK II
UEFI v2.40 (EDK II, 0x00010000)
Mapping table
BLK0: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>

Would you tell me how to resolve this issue and how to start Redhat OS?

[socratis]

When I update the guestaddition to 5.1.26 from 5.1.22

That's not called an update . Most probably a typo...

Why are you using EFI for your guest? Any particular good reason?

But, updating the Guest Additions (GAs) will not result in a non-bootable VM. Something else is going on...

• Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle.
• With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

[yasu]

Thank you for your comment.
It's not update. Just install same revision of guest addition.

According to your suggestion, I attached the Vbox.log after VM shut down.
I hope it is help for your analysis.

[yasu]

After I tried to change some environment setting, I could go display of OS selection.
When I select Redhad 7.2, VM stopped at line 1288 of attached "Vbox.log".
It seems to be a network problem.
I can enter VM using rescue mode.
Could you tell me how to do as next step?

[yasu]

Hello,
When I entered Redhat OS using rescue mode,
I found there were no files under /boot/efi.
Also /boot/grub2/grubenv -> /boot/efi/EFI/redhat/grubenv was not active.
I'm not sure this is the root cause or not.
But it seems to be related not to boot up OS.