Re: Planning for the next release

[Marius Bakke]

Ludovic Courtès <address@hidden> writes:

> Hi again!
>
> I build the installation image with from commit
> 96afb480f8165a315a69b1dd3a031e053044d3b2:
>
>   ./pre-inst-env guix system disk-image --image-size=1.2G 
> gnu/system/install.scm -K
>
> and then ran QEMU on that image:
>
>   qemu-system-x86_64 -enable-kvm -serial stdio \
>     -net nic,model=virtio -net user /tmp/t.qcow
>
> but that failed with:
>
> --8<---------------cut here---------------start------------->8---
> [    0.664746] RAMDISK: Couldn't find valid RAM disk image starting at 0.
> [    0.665664] List of all partitions:
> [    0.666117] 0100           65536 ram0 
> [    0.666118]  (driver?)
> [    0.666865] 0101           65536 ram1 
> [    0.666865]  (driver?)
> [    0.667602] 0102           65536 ram2 
> [    0.667602]  (driver?)
> [    0.668354] 0103           65536 ram3 
> [    0.668355]  (driver?)
> [    0.669062] 0104           65536 ram4 
> [    0.669063]  (driver?)
> [    0.669931] 0105           65536 ram5 
> [    0.669932]  (driver?)
> [    0.670675] 0106           65536 ram6 
> [    0.670675]  (driver?)
> [    0.671383] 0107           65536 ram7 
> [    0.671384]  (driver?)
> [    0.673712] 0108           65536 ram8 
> [    0.673716]  (driver?)
> [    0.675340] 0109           65536 ram9 
> [    0.675341]  (driver?)
> [    0.676810] 010a           65536 ram10 
> [    0.676812]  (driver?)
> [    0.677862] 010b           65536 ram11 
> [    0.677863]  (driver?)
> [    0.678739] 010c           65536 ram12 
> [    0.678740]  (driver?)
> [    0.679441] 010d           65536 ram13 
> [    0.679441]  (driver?)
> [    0.680144] 010e           65536 ram14 
> [    0.680145]  (driver?)
> [    0.680902] 010f           65536 ram15 
> [    0.680903]  (driver?)
> [    0.681675] 0800         1258291 sda 
> [    0.681676]  driver: sd
> [    0.682435]   0801         1207091 sda1 897ff0a1-01
> [    0.682436] 
> [    0.683158]   0802           40960 sda2 897ff0a1-02
> [    0.683159] 
> [    0.683872] 0b00         1048575 sr0 
> [    0.683873]  driver: sr
> [    0.684558] No filesystem could mount root, tried: 
> [    0.684559]  ext3
> [    0.685052]  ext2
> [    0.685253]  ext4
> [    0.685449]  vfat
> [    0.685645] 
> [    0.686013] Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(1,0)
> [    0.686831] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.11.0-gnu #1
> [    0.687689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
> rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
> [    0.690057] Call Trace:
> [    0.690475]  dump_stack+0x63/0x90
> [    0.690970]  panic+0xe4/0x22d
> [    0.691426]  mount_block_root+0x27c/0x2bf
> [    0.692042]  mount_root+0x65/0x68
> [    0.692424]  prepare_namespace+0x16a/0x1a2
> [    0.692872]  kernel_init_freeable+0x1f3/0x21c
> [    0.693348]  ? rest_init+0x80/0x80
> [    0.693720]  kernel_init+0xe/0x100
> [    0.694069]  ret_from_fork+0x2c/0x40
> [    0.694548] Kernel Offset: 0x2f000000 from 0xffffffff81000000 (relocation 
> range: 0xffffffff80000000-0xffffffffbfffffff)
> [    0.695494] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unknown-block(1,0)
> --8<---------------cut here---------------end--------------->8---

It looks like the initrd is becoming obese. Adding "-m 168M" makes it
boot (qemu defaults to 128MiB). Not sure what to do about it.

> Likewise, “make check-system TESTS=basic” fails like this:
>
> --8<---------------cut here---------------start------------->8---
> environment variable `PATH' set to 
> `/gnu/store/445x4k15v3mlym7n0i1irqyiih0hxr1f-qemu-minimal-2.9.0/bin:/gnu/store/ddpg6rlr5f3xv8fjh8812ll9g584x51z-parted-3.2/sbin:/gnu/store/bdzxdpdw25k8v6lz54clz42bilx47srj-grub-2.02/bin:/gnu/store/bdzxdpdw25k8v6lz54clz42bilx47srj-grub-2.02/sbin:/gnu/store/jh49klm0gkns071jsa8f9jr7g3cdlfwz-e2fsprogs-1.43.4/bin:/gnu/store/jh49klm0gkns071jsa8f9jr7g3cdlfwz-e2fsprogs-1.43.4/sbin:/gnu/store/82kq5zzq9d7rsq0d9rjppp3528p4cg72-dosfstools-4.1/sbin:/gnu/store/z763jk8lkragpz2qr2wbrz946lgalx2h-sed-4.4/bin:/gnu/store/87sj03j9kwzhl9zr76gs2i8ill86ki95-grep-3.0/bin:/gnu/store/6908gy3pws0ccys49ni98idwnicchlr2-coreutils-8.26/bin:/gnu/store/gdgrzf1y15scqwk1yzm51dc40g29vad9-findutils-4.6.0/bin:/gnu/store/55r4yg5iw9zh2j3zvzc6272k5xn4yxg4-gawk-4.1.4/bin'
> creating partition table with 2 partitions...
> parted: invalid option -- '1'
> parted: invalid option -- '9'
> parted: invalid option -- '9'
> parted: invalid option -- '2'
> parted: invalid option -- '2'
> parted: invalid option -- '9'
> parted: invalid option -- '4'
> parted: invalid option -- '4'
> parted: invalid option -- 'B'
> parted: invalid option -- '1'
> parted: invalid option -- '9'
> parted: invalid option -- '9'
> parted: invalid option -- '2'
> parted: invalid option -- '2'
> parted: invalid option -- '4'
> parted: invalid option -- '3'
> parted: invalid option -- '2'
> parted: invalid option -- 'B'
> Usage: parted [-hlmsv] [-a<align>] [DEVICE [COMMAND [PARAMETERS]]...]
> ERROR: In procedure scm-error:
> ERROR: failed to create partition table
>
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> [    1.032767] Kernel panic - not syncing: Attempted to kill init! 
> exitcode=0x00000000
> --8<---------------cut here---------------end--------------->8---

OMG. I've ran the other system tests, but somehow missed "basic". Oops!

Anyway, the problem is that the parted script gets a negative size for
TESTS=basic:

creating partition table with 2 partitions...                                   
      
DEBUG: (mkpart primary ext2 1048576B -19922944B set 1 boot on mkpart primary 
ext2 -19922432B 22020608B set 2 esp on)

The attached commit fixes it; although there are other default sizes in
(gnu system vm) that may need adjustment after
ecf5d5376979fadd971559367bf553df89fcc62b.

Currently running *all* system tests, but it's going to take a while!

0001-vm-Increase-default-disk-sizes-to-account-for-ESP-pa.patch
Description: Text Data

signature.asc
Description: PGP signature