﻿ticket,summary,version,created,modified,_changetime,_description,_reporter
19729,VM failed to start with enabled EFI,VirtualBox 6.1.10,2020-07-17T11:44:12Z,2021-03-18T09:25:50Z,2021-03-18T09:25:50Z,"Approx. every tenth start/boot of the vm failed due to enabled EFI.
Failed means: the vm window opens and not output occurs.
This behavior can be seen on VBox version 6.1.10 r138449 (Qt5.6.2) and on older 
version 6.0.8 r130520 (Qt5.6.2).


",benni
20468,VM crashes during reboot if EFI is used on Ryzen CPU,VirtualBox 6.1.24,2021-07-21T22:23:17Z,2021-07-21T23:58:34Z,2021-07-21T23:58:34Z,"Guru crash dialog during reboot of EFI Windows 10 VM upon the way back up at the EFI screen when more than 1 vCPU is used.  I have a Ryzen 7 3700X CPU on a B550M chipset motherboard.
Reference forum post https://forums.virtualbox.org/viewtopic.php?f=1&t=103398&sid=5b8fb3bf048f3b4fda4d91bcbd9ec0d3.  User fth0 looked at the logs and found that ""vCPU1 (the second vCPU) is in real mode and triple-faults"".

Logs attached.
",Justinh
19176,VirtualBox 6.1: Can't attach Nvram Storage driver (VERR_PDM_DRIVER_NOT_FOUND),VirtualBox 6.1.0,2019-12-20T09:54:53Z,2021-03-19T19:55:14Z,2021-03-19T19:55:14Z,"Setting any NVRAM variables (`VBoxInternal/Devices/efi/0/LUN#0/Config/Vars/`) results in the error `Can't attach Nvram Storage driver (VERR_PDM_CFG_MISSING_DRIVER_NAME)`

Setting the driver name as it was in VirtualBox 6.0 and earlier (`VBoxManage setextradata VMname 'VBoxInternal/Devices/efi/0/LUN#0/Driver' 'NvramStorage'`) results in the error `Can't attach Nvram Storage driver (VERR_PDM_DRIVER_NOT_FOUND)`.

VirtualBox 6.0 powers on the VM fine, 6.1 doesn't power on with the above errors.",Jack_Smith
20743,VBox 6.1.x does not boot FreeBSD EFI,VirtualBox 6.1.30,2021-12-23T00:22:56Z,2021-12-23T00:22:56Z,2021-12-23T00:22:56Z,"Vbox 6.0.24 (or older) boots (FreeBSD) EFI images just fine.
Vbox 6.1.x (I've tried all versions) does not boot EFI but instead goes to network boot even if that's disabled for the VM.",adwsklerjuihgweiop
21278,UEFI Linux guest fails to boot in VB 7,VirtualBox-7.0.2,2022-11-16T20:35:08Z,2023-02-10T10:08:12Z,2023-02-10T10:08:12Z,I upgraded to VB 7 on Monterey 12.6 and it fails to boot a Linux-based guest in UEFI mode. Log attached.,mauricev1
17326,Serial ports do not work correctly,VirtualBox 5.1.30,2017-11-29T05:46:08Z,2017-12-02T06:15:06Z,2017-12-02T06:15:06Z,"Only serial ports COM1 and COM2 work in EFI mode. Any other serial port configurations are either not detected or do not perform any requested actions. EFI_SERIAL_IO_PROTOCOL seems to not be reliable in writing to the serial port, timeout happens before the timeout could have possibly passed, set to multiple seconds and it fails instantly. Trying to solve this by writing in a loop produces incorrect results as the size written is incorrectly reported so some data gets written multiple times. Also, garbage is always written to a serial port when the machine is started, sometime during post. This can be proven by assigning COM1 or COM2 to a Raw file output. I have attached an two examples. I have tested this in Windows, Linux, and macOS, so it appears to be a core EFI issue.",apianti
9390,Mac OS X guest video memory remains on 4MB. It does not use the video memory setting of the guest configuration.,VirtualBox 4.1.0,2011-08-06T09:12:58Z,2015-09-10T02:57:35Z,2015-09-10T02:57:35Z,It does not matter what setting you choose for video memory (0 - 128 MB) for a Mac OS X server guest. The guest OS always reports that there is only 4MB screen memory available. Please see my attached screen shots for the guest Os report. This is evident when trying to use screen share to the guest OS. The screen share quality is in very low. This also could be the cause of the jerky graphics inside the guest OS normal operation eg. the menu navigation. ,Pieter
19211,Guest won't boot in EFI mode after deleting/adding main disk file,VirtualBox 6.1.0,2020-01-08T16:50:31Z,2021-03-18T09:26:14Z,2021-03-18T09:26:14Z,"Setup:
2 VDI disks.
EFI mode enabled (the main disk can only boot in EFI mode).
Hard disk as first device in System/Boot order VM settings.
Regular rebuild of disk images: regular re-add of those images in the storage settings.

After update to VBox 6.1.0, we encountered a bug where after removing and re-adding the bootable media (VDI disk) from the VM storage settings, it won't be able to boot anymore.

It tries to boot in PXE mode and drops into an EFI shell after some time.
I can boot by running the bootx64.efi executable from the shell.

When entering the bios/uefi menu (after exiting EFI shell), we can see that the disk is not in the boot options anymore, there are only PXE and EFI shell.

Reverting to 6.0.14 make it works as expected (boot correctly after disk change).",vclement
20262,"FreeBSD host, EFI guests, 6.1.18: F12 no longer presents the boot manager",VirtualBox 6.1.18,2021-03-18T09:03:33Z,2021-03-19T19:33:45Z,2021-03-19T19:33:45Z,"With 5.2.44, if I recall correctly: 

* F12 always successfully presented the boot manager. 

With recent https://svnweb.freebsd.org/ports?view=revision&revision=567950 for the ports collection for FreeBSD: 

* 6.⋯ became available (nothing earlier than 6.1.18 was in the collection)
* end of life 5.2.44 became legacy. 

With 6.1.18, it seems: 

* boot management is impossible for guests that use EFI. 

The VirtualBox splash screen appears for no longer than a split-second (with and without keying F12), then there's the shell. 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878#c235 (comment 235) described the symptom but was – in the context of bug 234878 (emulators/virtualbox-ose: Update to 6.1) – ''not'' a show-stopper. ",Graham Perrin
19386,FileVault,VirtualBox 6.1.4,2020-03-08T11:46:20Z,2021-04-30T07:12:52Z,2021-04-30T07:12:52Z,"VirtualBox successfully boots macOS Sierra, High Sierra, Mojave, or Catalina, and these operating systems allow encrypting volumes with FileVault2. Attempting to boot a FileVault2-encrypted volume in VirtualBox 6.1.4 or lower results in several boot errors, most importantly `**** ERROR _LoginUIInitializedGraphics Can't install updated AppleEvent protocol`. The FileVault login UI will not load, probably because macOS cannot find or use the VirtualBox EFI implementation of the UEFI Graphics Output Protocol.

An open-source (BSD 3-clause license) implementation of this graphics protocol is available through the [https://github.com/acidanthera/OpenCorePkg/blob/master/Library/OcConsoleLib/ConsoleGop.c OpenCore ConsoleGop.c] source file.

The FileVault2 prompt can be successfully loaded by loading OpenCore through the EFI Internal Shell, and macOS boots normally when the correct password is provided.

Maybe this protocol can be implemented in VirtualBox so FileVault could work without the OpenCore bootloader.

Log files are not attached because the error doesn't show up in the log, only the normal VM startup and shutdown procedures.

----

Steps to reproduce:
* Install any version of macOS Sierra, High Sierra, Mojave, or Catalina (and probably other versions that use FileVault2)
* Encrypt the system volume with FileVault2 (called simply FileFault in System Preferences).
* Reboot. The macOS kernel will not be able to load the FileVault password prompt.

Workaround:
* Load OpenCore.efi through the EFI Internal Shell with `ProvideConsoleGop` set to `true`. The password prompt will be displayed and the FileVault volume can be decrypted, continuing normal boot.",Jack_Smith
20207,EFI: Incorrect behavior of ExitBootServices,VirtualBox 6.1.18,2021-02-19T17:00:21Z,2021-03-19T19:46:01Z,2021-03-19T19:46:01Z,"After executing ExitBootServices function, all CPUs except boot one should be initial state. In current version of EFI, CPUs continue to execute EFI firmware code. If you then overwrite data structures assigned for page tables, then crash will occur.
Log fragment: 
00:00:10.797876 Guest CPUM (VCPU 1) state: 
00:00:10.797878 eax=00000640 ebx=00000000 ecx=3e8aaa00 edx=00000000 esi=3ed6d01a edi=3e8a8440
00:00:10.797879 '''eip=3ed6d05f esp=3ed6cf80''' ebp=00000000 iopl=0         nv up di nt zr ac po cy",shmkv
21083,EFI shell fails to detect non-ESP partitions,VirtualBox 6.1.36,2022-08-29T19:26:43Z,2022-08-29T19:29:32Z,2022-08-29T19:29:32Z,"Starting with 6.1.34, EFI (both shell and ""GUI"") fails to detect non-ESP partitions in optical media.  Booting from the media using the included boot loader works.  However, it's no longer possible to bypass the boot loader and boot directly from the non-ESP partitions.

I've tested a Windows 10 host with VirtualBox 6.1.34 and 6.1.36.  I've observed the problem with debian-11.2.0-amd64-netinst.iso, ubuntu-22.04-live-server-amd64.iso, and FreeBSD-13.0-RELEASE-amd64-disc1.iso.

This worked in 6.1.32.",ov2k
19364,EFI boot from ISO does not work in existing VMs,VirtualBox 6.1.4,2020-02-29T08:49:36Z,2022-10-04T20:24:36Z,2022-10-04T20:24:36Z,"I have installed Windows 10 64 Bit as guest in EFI mode in a VM under Windows 10 64 Bit as host system, it works fine. However when I mount a bootable ISO (e. g. an actual Windows 10 ISO) and set the optical device as first option in the boot priority, the machine still boots the installed Windows 10 from hard disk. Obviously the boot order is without any effect.
When I create a new VM in EFI mode, booting from ISO works one time, when I close the dialog, which asks the boot medium.
In legacy guest mode (without EFI) everything works fine.
I found this bug first time in Virtual Box 6.1.",awhb
19956,Disk booting no longer works automatically on EFI system after cdrom is removed,VirtualBox 6.1.14,2020-10-10T18:31:05Z,2021-03-19T19:45:35Z,2021-03-19T19:45:35Z,"I am able to install devuan 32 bit and 64 bit to respective EFI VMs.  This involves navigating the UI and possibly booting from the EFI shell to coerce vbox to boot the install media.  However, after the install is complete, vbox correctly boots to the grub menu the installation media installed.

A problem arises, however, if I insert any arbitrary CD into the cdrom device.  Any attempt to boot off the CD requires navigating the UI again, and in most cases, requires booting from the EFI shell no matter what combination of options I select (such as deleting all but the Cdrom from the boot options and even changing the boot order).  There does not seem to be any way to get vbox to boot off the hard drive after a cd has been inserted and removed.

This behavior appears to be consistent across 32 and 64 bit EFI VMs.

Steps to reproduce:

* Create new EFI VM
* launch installer CD (most likely from EFI Shell, since vbox won't launch the CD automatically)
* complete the install and reboot from hard drive
* insert any CD into the drive
* attempt reboot
* remove the CD from the drive
* attempt to reboot from hard drive again

Expected Results:

VM will return to booting from the hard drive without needing to do anything; the grub menu will appear as normal.

Actual Results:

If the scenario is reproduced, vbox will not boot off the hard drive by itself.  It will be necessary to launch from navigating and selecting via the UI or by using the EFI shell",Harry M
17013,CustomTable not present in EFI mode,VirtualBox 5.1.26,2017-08-14T21:25:34Z,2021-03-19T19:54:09Z,2021-03-19T19:54:09Z,"{{{
VBoxManage setextradata ""VM name"" ""VBoxInternal/Devices/acpi/0/Config/CustomTable"" ""/path/to/table.bin""
}}}
(see UserManual: 9.13 Configuring the custom ACPI table)
doesn't work properly for VMs in EFI mode (but in BIOS mode).

It seems the implementation under [https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/EFI/Firmware/MdeModulePkg/Universal/Acpi/AcpiPlatformDxe/AcpiPlatform.c AcpiPlatform.c] Revision 58975 line 220 isn't present. There is no entry in ""TableInfo[]""

''' * To reproduce *'''

 1. Create a VM with EFI mode
 2. Set extra data using VBoxManage
 3. Configure custom ACPI table
 4. boot linux (like CloneZilla) in shell mode 
 5. `ls -l /sys/firmware/acpi/tables/`

The expected table isn't present. Switch to BIOS mode works correct.",vboooo
14842,Converting OVA-deployed machine to EFI gives Error: No mapping found.,VirtualBox 5.0.10,2015-11-18T14:10:02Z,2021-03-19T19:54:16Z,2021-03-19T19:54:16Z,"I'm generating OVA template which is intended to be tested for BIOS and UEFI boot capabilities. There is no problem with regular workflow, deploy machine, turn it on and continue with BIOS boot. But once I've turned on ""Enable EFI"" options in deployed machine settings I've got error from UEFI interactive shell - Error: No mapping found. It seems VirtualBox doesn't generate UEFI default boot entries for OVA-deployed instance. Could it be fixed?",Roman Valov
21217,Cannot boot from VISO,VirtualBox 6.1.40,2022-10-29T19:09:38Z,2022-10-29T19:09:38Z,2022-10-29T19:09:38Z,"I have been struggling to boot an extracted Windows 11 medium using a VISO file without success until I found a comment regarding this topic:
https://www.virtualbox.org/ticket/19910#comment:24

They mention that on 6.1.32 booting from VISO worked fine which I can confirm.
However, I could not get it to work with VB 6.1.38, 6.1.40, 7.0.0 or 7.0.2.",Flubberlutsch
