VirtualBox with EFI-enabled
Message-Id: <20160818003938.a21a906e15d2a2e67bdf4...@debian.or.jp>
In-Reply-To: <20160429231623.gu5...@einval.com>
Organization: Debian JP Project
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
On Sat, 30 Apr 2016 00:16:23 +0100 Steve McIntyre <st...@einval.com> wrote:
> Do we know what version of Virtualbox?
Still occurs, from 5.0.24 (on Debian Sid) to 5.1.2 and 5.1.4 (on Windows10).
And now I found why other distro can boot on UEFI enabled Virtualbox.
- Booting from UEFI shell by kicking /boot/efi/EFI/debian/grubx64.efi works.
- Fedora24 on Virtualbox can boot without UEFI shell, and it has different
files in its /boot/efi partition, especially /boot/efi/EFI/BOOT/BOOTX64.EFI
and /boot/efi/EFI/BOOT/fallback.efi . Once delete those files, Fedora24
won't boot.
- Just copying those files to Debian on VirtualBox won't boot, it just repeats
showing error and rebooting.
Probably VirtualBox UEFI seeks /boot/efi/EFI/BOOT, not
/boot/efi/EFI/${distro}.
I don't know this behavior is okay or not, but it's better to add workaround
to d-i, IMHO (for users' convenient).
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
