[Bug 1100386] Re: Server installations on VMs fail to reboot after the installations

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 202-0ubuntu7

---------------
systemd (202-0ubuntu7) saucy; urgency=low

  [ Martin Pitt ]
  * debian/*: Replace remaining "udevadm info --run" invocations with
    /run/udev/. (LP: #1182788)
  * Add 0020-persistent-storage-rule-mmc-partname.patch: Create disk/by-name
    links for mmcblk partitions if they have a PARTNAME property. Patch by
    Ricardo Salveti de Araujo, taken from udev 175-0ubuntu29.

  [ Andy Whitcroft ]
  * debian/extra/rules/78-graphics-card.rules -- demote efifb to a secondary
    display adaptor as in the majority of cases this will be replaced by
    a DRM driver.  (LP: #1100386)
 -- Martin Pitt <martin.pitt at ubuntu.com>   Wed, 22 May 2013 12:09:59 +0200

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1100386

Title:
  Server installations on VMs fail to reboot after the installations

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “udev” package in Ubuntu:
  Invalid
Status in “linux” source package in Raring:
  Won't Fix
Status in “systemd” source package in Raring:
  Invalid
Status in “udev” source package in Raring:
  In Progress

Bug description:
  Raring and saucy server installations with both amd64 and i386 fail to
  reboot normally after the installations on VMs. This occurs with both
  amd64 and i386 images when installing VMs, (using libvirt and virt-
  manager and also using VirtBox).

  This appears to be a regression started with Ubuntu 3.7.0-6-generic.
  Earlier versions do not have this issue.

  On i386 installations booting via the recovery mode causes "Kernel
  panic - not syncing: Attempted to kill init! exit code 0x00000600" as
  shown in the attached image.

  Latest amd64 (20130121) installations with virtual-host package
  selection also reported the kernel panic when booting via recovery
  mode with the same message above, "Kernel panic - not syncing:
  Attempted to kill init! exit code 0x00000600".

  Standard booting causes the similar type of hang as that in i386
  cases. (please see the video attached)

  This issue can not be seen in hardware installations.

  Steps to reproduce:

  A) Manual steps:

  1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
  2. Reboot after the grub installation is complete

  B) Automated steps:
  1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
  2. Reboot the machine
  (I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
  The steps are
  1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
          sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
  2. Reboot the VM after the installation

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