← Back to team overview

touch-packages team mailing list archive

[Bug 1421117] Re: fails to boot with "Attempted to kill init" in VMWare, absolute /sbin/init symlink does not work

 

Correct, ubuntu defaults to pulling in busybox-static into initramfs if
available. In practice, we pretty much require it for all our initramfs
and rarely don't have it. Maybe it should become a hard dependency on
ubuntu?

However, given that we support booting with either systemd or upstart,
shouldn't our initramfs search for /sbin/upstart or /lib/systemd/systemd
direct rather than /sbin/init?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools 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 initramfs-tools package in Ubuntu:
  In Progress

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/initramfs-tools/+bug/1421117/+subscriptions


References