touch-packages team mailing list archive

[Michael Bienia <michael@xxxxxxxxx>]

I managed to some more output to the serial log (booted with
"console=ttyS1,115200" only, no "console=tty0"):

starting version 219
[    1.851984] sd 2:0:0:0: [sda] Assuming drive cache: write through
/init: line 307: chroot: not found
Target filesystem doesn't have requested /sbin/init.
/init: line 325: chroot: not found
/bin/sh: 0: Can't open splash
[    2.909334] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1421117

Title:
  fails to boot with "Attempted to kill init" in VMWare, absolute
  /sbin/init symlink does not work

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after permanently switching to systemd.
  I've switched to systemd with "apt install systemd-sysv --purge" (it only purged the upstart package) and with the default "Ubuntu" entry the boot fails after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it works when edit the grub entry (in the grub shell) and add "init=/lib/systemd/systemd".

  Attached is the serial output (with "debug" but no "init=" parameter).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421117/+subscriptions