[elbe-devel] elbe initvm attach -> login does not work after upgrading from 1.1 to 1.2 stable

Manuel Traut manuel.traut at linutronix.de
Wed Dec 13 06:21:29 CET 2017


Hi Lukasz,

On Tue, Dec 12, 2017 at 04:40:05PM +0000, Lukasz Walewski wrote:
> >-----Ursprüngliche Nachricht-----
> >Von: Manuel Traut [mailto:manuel.traut at linutronix.de]
> >Gesendet: Montag, 6. November 2017 16:48
> >An: Lukasz Walewski
> >Cc: elbe-devel at linutronix.de
> >Betreff: Re: [elbe-devel] elbe initvm attach -> login does not work
> >after upgrading from 1.1 to 1.2 stable
> >
> >Hi Lukasz,
> >
> >On Fri, Sep 08, 2017 at 02:54:26PM +0000, Lukasz Walewski wrote:
> >> Hi,
> >>
> >> I think Frank meant Debian 9.0 (stretch) here. Under Debian 8.9
> >(jessie) the fix does not work. I upgraded my jessie VMware VM today,
> >which included Elbe upgrade to version 2.1 (from
> >http://debian.linutronix.de/elbe jessie main). Creating a fresh initvm
> >results in an error:
> >>
> >> $ elbe --version
> >> elbe v2.1 debian 8.9
> >>
> >> $ elbe initvm create
> >> [...]
> >> touch .stamps/stamp-create-buildenv-img
> >> /usr/bin/kvm
> >> qemu-system-x86_64: -M pc-i440fx-2.6: Unsupported machine type
> >> Use -machine help to list supported machines!
> >>
> >> So obviously the pc-i440fx-2.6 is not available in jessie, however, it
> >is requested by the Makefile if running under VMware:
> >>
> >> $ cat initvm/Makefile
> >> MEMSIZE?=1024
> >> SMP?=`nproc`
> >> INTERPRETER?=/usr/bin/kvm
> >>
> >> # this is a workaround for
> >> # http://lists.linutronix.de/pipermail/elbe-devel/2017-
> >July/000541.html
> >> VIRT=$(shell test -x /usr/bin/systemd-detect-virt && /usr/bin/systemd-
> >detect-virt)
> >> ifeq ($(VIRT), vmware)
> >> MACHINE?=pc-i440fx-2.6
> >> else
> >> MACHINE?=pc
> >> endif
> >>
> >> Wasn't this workaround meant for stretch and not for jessie?
> >
> >probably yes. I don't have a test setup for this.
> >Can you add a check for
> >
> >'lsb_release -c' == stretch
> >
> >to the Makefile.mako. And provide a patch for this?
> 
> Please find attached the requested patch. I tested it on the current Debian 8.x (stretch) with elbe v2.2, which makes kvm to boot as expected:

thanks, i'll have a look, after the installer problem..

> jessie:~$ elbe initvm create
> ...
> touch .stamps/stamp-create-buildenv-img
> /usr/bin/kvm
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Initializing cgroup subsys cpuacct
> [    0.000000] Linux version 3.16.0-4-amd64 (debian-kernel at lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.39-1 (2016-12-30)
> [    0.000000] Command line: root=/dev/vda1 debconf_priority=critical console=ttyS0,115200n1 DEBIAN_FRONTEND=text
> 
> However, the whole "initvm create" fails on the partitioning stage, which is probably unrelated to the selection of the VM type:
> 
> ...
> Starting up the partitioner  ... 13%... 22%... 31%... 40%... 50%... 63%... 72%... 81%... 90%... 100%
> Guided partitioning  ... 20%... 40%... 60%... 80%
> Partitions formatting  ... 33%
> Partition disks
> ---------------
> 
> The attempt to mount a file system with type ext3 in Virtual disk 1, partition
> #1 (vda1) at / failed.
> 
> You may resume partitioning from the partitioning menu.
> Do you want to resume partitioning?
>   1: Yes [*]  2: No
> Prompt: '?' for help, default=1>
> 
> Any hints how to fix this?

The problem is in the debian installer, if you answer the question with No and
go to a shell:

~ # insmod /lib/modules/3.16.0-4-amd64/kernel/fs/ext4/ext4.ko
insmod: ERROR: could not insert module /lib/modules/3.16.0-4-amd64/kernel/fs/ext4/ext4.ko: Unknown symbol in module

The installer is provided by the 'elbe-bootstrap' package. Probably Debian
uses a new kernel in Debian 8.10 released on 9th of December. So the old
Kernel provided by elbe-bootstrap is not able to load the 'newer' kernel modules
downloaded from the configured primary mirror.



More information about the elbe-devel mailing list