Processed: Re: Bug#822941: debian-installer: cannot boot installed on
Processing control commands: > tag -1 +wontfix Bug #822941 [debian-installer] debian-installer: cannot boot installed on VirtualBox with EFI-enabled Added tag(s) wontfix. -- 822941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822941: debian-installer: cannot boot installed on
Control: tag -1 +wontfix On Fri, Aug 19, 2016 at 07:12:17AM +0900, Hideki Yamane wrote: >control: reopen -1 >control: tag -1 -moreinfo > >On Wed, 17 Aug 2016 17:17:49 +0100 >Steve McIntyrewrote: > >> > 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. > > Thanks, it is very helpful to understand this issue. > > And I want to propose you to add workaround for VirtualBox via exec > force_efi_extra_removable _automatically_. If d-i detects it runs on VBox, > then install /boot/efi/EFI/BOOT/*.efi is better for users. Probably VBox users > who want to install Debian can ignore co-exist other OSes since they don't > do such installation (that is VM!), so no any harm. You can know if it is > installed on VBox by running dmidecode. > >>$ sudo dmidecode -s baseboard-product-name >>VirtualBox > > And also, maybe collecting information for broken UEFI hardware and > add such workaround is better feature for users. > (Yes, I know it's dirty workaround but it's really handy). I *really* don't want to go down that route. It's bad enough that there are broken *real* systems out there which don't work properly with UEFI, and it's very difficult to tell from userland which systems are likely to work and which won't as firmware fixes may happen any time. Adding a hacky workaround for broken initial UEFI support in a virtualistion platform is ludicrous here - if you're using VirtualBox then install without UEFI, or if you must use the *experimental support* for EFI in VirtualBox [1] use the documented option which is available already via the d-i expert menu or through preseeding. [1] https://www.virtualbox.org/manual/ch03.html#efi -- Steve McIntyre, Cambridge, UK.st...@einval.com "When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 834601 installation-reports: installation screens don't display > properly on qemu VM Bug #834601 [installation-reports] installation-reports Changed Bug title to 'installation-reports: installation screens don't display properly on qemu VM' from 'installation-reports'. > thanks Stopping processing here. Please contact me if you need assistance. -- 834601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#834806: installation-reports - 2016.08.19 08:30 am CEST
Package: installation-reports Boot method: netboot PXE Image version: https://d-i.debian.org/daily-images/i386/daily/netboot/netboot.tar.gz [time stamp: 2016-08-19 00:39] Date: 2016.08.19 08:30 am CEST Machine: Windows7 + VirtualBox Processor: generic VirtualBox 1 CPU Memory: Generic VirtualBox 512 MB Partitions: default debian-installer LVM disk partitioning (one partition for all) Output of lspci -knn (or lspci -nn): N/A (installation broken on base install) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[*E*] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: During the "Install the base system" Debootstrap warning about base packages failure pops up. Two issues discovered: 1. mkdir of few /target/dev/ files fails - syslog error says files already exist - /target/dev/null, zero, full + some others. Solution: removing this files (or all) and running this step again solves the issue. 2. dpkg: dependency problems prevent configuration of gnupg: gnupg1 (1.4.20-7) breaks gnupg (<<1.4.20.-6+exp1) and is installed. Version of gnupg to be configured is 1.4.20-6