To be clear this was fixed in raring with:

lxc (0.8.0~rc1-4ubuntu45) raring; urgency=low

  [ Stéphane Graber ]
  * Allow the container to mount efivars on /sys/firmware/efi/efivars.
    efivars is automatically mounted by mountall on UEFI systems, failure to
    do so leads to a complete boot failured.
  * Allow mounts and pivot_roots under /usr/lib/lxc/root/ for compatibility
    with nested precise lxc hosts (quantal -> precise -> containers).

  [ Serge Hallyn ]
  * update 0227-ubuntu-cloud-parsing to catch a doc typo stgraber had found
    in the upstream review.
  * 0228-ignore-kmsg-setup-failure: ignore failure to set up kmsg, since that
    is not critical.

  [ Christian Kampka ]
  * Have upstart run lxc instances (LP: #1049908)

 -- Serge Hallyn <serge.hal...@ubuntu.com>  Tue, 27 Nov 2012 22:52:10
-0600


** Changed in: lxc (Ubuntu Quantal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1097312

Title:
  container startup must not fail if setup_kmsg fails

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to