touch-packages team mailing list archive

[Michael Bienia <michael@xxxxxxxxx>]

Public bug reported:

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).

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "SerialOutput.txt"
   https://bugs.launchpad.net/bugs/1421117/+attachment/4317802/+files/SerialOutput.txt

-- 
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:
  Ubuntu 15.04 VM doesn't boot after switching permanently to systemd

Status in systemd package in Ubuntu:
  New

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