Bug#825793: Installing the lilo bootloader on a qemu/kvm VM fails
Package: installation-reports
Severity: important
Tags: d-i
Installing lilo bootloader on qemu/kvm virtual machine fails.
-- Package-specific info:
Boot method: CD
Image version: http://cdimage.debian.org/cdimage/stretch_di_alpha6/amd64/iso-cd/debian-stretch-DI-alpha6-amd64-netinst.iso
Date: <Date and time of the install>
Machine: qemu/kvm using virt-manager
Partitions: <df -Tl will do; the raw partition table is preferred>
(I cannot cut-and-paste from the virt-viewer, but here is an abridged
summary, typed by hand)
/dev/vda1 is mounted on both /target and /dev/.static/dev.
/dev/sr0 is mounted on both /target/media/cdrom0 and /cdrom.
sfdisk -l /dev/vda gives
Device Boot Start End Sectors Size Id Type
/dev/vda1 2048 14678015 14675968 7G 83 Linux
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: [O]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Install tasks: [O]
Install boot loader: [E]
Overall install: [ ]
Comments/Problems:
I created a virtual machine using virt-manager and used the stretch DI
alpha 6 netinst to install Debian. I selected expert (non-graphical)
install. I used manual partitioning to create a single partition
without a swap partition. The other options were defaults, except for
things like hostname and initial user (no root login). When I skipped
"Install GRUB boot loader" and selected "Install LILO boot loader", then
selected "/dev/vda: Master Boot Record", I get the "Installation step
failed" dialog.
As a side note, the actual command that failed and the output from that
command would help immensely. The idea that "technical output" scares
users is flawed; when something goes wrong, even if the user is unable
to understand the lower level diagnostics, providing it allows the user
to find help more easily and/or provide more useful bug reports.
I am going to guess (and this is just a guess) that what I would have
seen, had the output to the command been visible, was either
/bin/sh: liloconfig: not found
or
/bin/sh: lilo: not found
as switching to another console shows that neither command is installed.
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to submit@bugs.debian.org.
I have snipped the installer-hardware summary, as I believe the host
environment is completely irrelevant to this bug, other than it is an
amd64 architecture. If there is a specific piece of information that
would help in the diagnosis, I will be more than happy to provide it.
I am using libvirt-clients, libvirt-daemon, and libvirt-daemon-system
version 1.3.3-2; virt-manager 1:1.3.2-4; qemu 1:2.5+dfsg-5+b1.
Thanks...Marvin
Reply to: