[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 Tue, 13 Apr 2021 16:02:14 +0200 (CEST)
with message-id <alpine.DEB.2.21.2104131552270.17262@hier>
and subject line UEFI install on Virtual Box should be fixed with VB 6.1
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: https://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 --- 
Lennart Sorensen wrote:


On Wed, Aug 24, 2016 at 09:30:15AM +0200, Philipp Kern wrote:
I agree. Especially keying off the vendor name here when the expectation is that they fix the bug (in which case the workaround should not be applied anymore). However, has a bug actually been filed with VirtualBox about this behavior? 

The Documentation for VirtualBox essentially says UEFI is for MacOS
and not general purpose and that they don't implement the UEFI variable
storage.  Their workaround is to use a startup.nsh script to boot.
Doing that does work just fine.

So at least for now they don't think it's a bug.  It is working as
designed (even though the design is clearly shit for no good reason).

https://www.virtualbox.org/ticket/11177 has their explanation of their
bad design.


https://www.virtualbox.org/ticket/11177#comment:4 says:


  Status changed from new to closed
  Resolution set to fixed
Proper NVRAM handling has finally materialized with VirtualBox 6.1, closing as fixed.
So it seems that the problem has been fixed in VirtualBox 6.1 (which it seems will *not* be part of the Debian bullseye release).
So I assuming this bug report can be closed, which I'm doing herewith. Please reopen if the broken behavior remains or if you disagree (this bug report has a won't fix - so maybe it should stay open with wontfix for older VirtualBox/debian-installer combinations?)
Thanks to everybody contributing/helping here: Steve, Philipp, Lennart, Hideki, aeichner@VirtualBox, 
*t

--- End Message ---
Reply to: