** Summary changed:

- Raring server installations on VMs fail to reboot after the installations
+ Server installations on VMs fail to reboot after the installations

** Description changed:

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

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to