[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#822941: marked as done (debian-installer: cannot boot installed on VirtualBox with EFI-enabled)

Your message dated Wed, 17 Aug 2016 17:17:49 +0100
with message-id <20160817161749.GA8169@einval.com>
and subject line Re: Bug#822941: debian-installer: cannot boot installed on
has caused the Debian Bug report #822941,
regarding debian-installer: cannot boot installed on VirtualBox with EFI-enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
822941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822941
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: important

Dear Maintainer,

 I found user notes Debian on VBox with EFI enabled environment cannot
 boot, see http://qiita.com/zakuro9715/items/45e82473ce39914e04ed (in Japanese)

 I've confirmed it with d-i9 alpha5.
 And, it doesn't happen with Fedora 24 alpha and Ubuntu 16.04.


Step to reproduce:

 1. setup Virtualbox VM with EFI enabled
 2. install Debian
 3. after installation, turn of VM
 4. turn on VM again
 5. not bootable, startup EFI shell



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Thu, Aug 18, 2016 at 12:39:38AM +0900, Hideki Yamane wrote:
>
>On Sat, 30 Apr 2016 00:16:23 +0100 Steve McIntyre <steve@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.

Right, that's exactly what I described in my last mail about this
bug. If Fedora is installing to the removable media path as a default,
that is *broken* and *wrong*. This is masking missing UEFI support in
VirtualBox - it's not saving UEFI variables persistently like qemu
does when using UEFI.

> 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).

There's already support for doing this in d-i for the sake of
supporting broken firmware implementations. See

  https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path

for more information. It's even preseedable. So I'm closing this bug.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

--- End Message ---
Reply to: