Package: installation-reports
Boot method: Connected ISO to the VM, set it as the boot priority in
virt-manager
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
(19-Aug-2010 05:50)
Date: 01:00 19 August 2010 UTC-5
Machine: KVM virtual machine running on a home-built system, Ubuntu
10.04 host OS
Processor: KVM virtual processor / Phenom II X4 905e
Memory: 512 MB allocated / 8GB G.Skill Ripjaws
Partitions: None initially, chose the option of autopartition with LVM
and separate /home
Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
[Natoma] [8086:1237] (rev 02)
Subsystem: Qumranet, Inc. Qemu virtual machine [1af4:1100]
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
[Natoma/Triton II] [8086:7000]
Subsystem: Qumranet, Inc. Qemu virtual machine [1af4:1100]
00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II] [8086:7010]
Subsystem: Qumranet, Inc. Qemu virtual machine [1af4:1100]
Kernel driver in use: ata_piix
00:01.2 USB Controller [0c03]: Intel Corporation 82371SB PIIX3 USB
[Natoma/Triton II] [8086:7020] (rev 01)
Subsystem: Qumranet, Inc. Qemu virtual machine [1af4:1100]
Kernel driver in use: uhci_hcd
00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 03)
Subsystem: Qumranet, Inc. Qemu virtual machine [1af4:1100]
Kernel driver in use: piix4_smbus
00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8]
Subsystem: Qumranet, Inc. Device [1af4:1100]
00:03.0 Ethernet controller [0200]: Qumranet, Inc. Virtio network
device [1af4:1000]
Subsystem: Qumranet, Inc. Device [1af4:0001]
Kernel driver in use: virtio-pci
00:04.0 SCSI storage controller [0100]: Qumranet, Inc. Virtio block
device [1af4:1001]
Subsystem: Qumranet, Inc. Device [1af4:0002]
Kernel driver in use: virtio-pci
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]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [E]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
I choose the tasks for desktop install, web server, sql database, ssh
server, and basic utilities. Things download okay, and I believe
start to install, but shortly thereafter I get the red error screen of
"an installation step failed". Upon switching VTs and poking around,
I discovered in /var/log/syslog that dpkg was failing due to running
out of disk space. 'df' confirms that the tmpfs on on
/dev/.static/dev and /dev/mapper/debian--testing-root on /target were
both full, with a size of 2.2G. I had granted 8GB of total disk space
to the VM. 5.1G were being used for /dev/mapper/debian--testing-home
on /target/home.
In short, I think the "automatically partition the disk" option isn't
giving itself enough space to work with in this admittedly unusual
configuration.
I ran through a second time only choosing the desktop and basic
utilities tasks, and that went through without a hitch. While this is
a fairly outside case that doesn't necessarily need to succeed, it
would be nice to at least have some logic to fail more gracefully /
informatively, whether that be saying that it failed due to
insufficient disk space, or better yet, telling the user after they've
selected tasks that they won't have enough room for those selections.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
