Also affected, I was able to get the system to boot by adding
systemd.mask=tmp.mount to the kernel command line, but I have no DNS
once the desktop environment boots, and shutdown hangs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
*** This bug is a duplicate of bug 1736116 ***
https://bugs.launchpad.net/bugs/1736116
** This bug is no longer a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
** This bug has been marked a duplicate of bug 1736116
[SRU] Host
*** This bug is a duplicate of bug 1736116 ***
https://bugs.launchpad.net/bugs/1736116
** This bug has been marked a duplicate of bug 1736116
[SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
--
You received this bug notification because you are a member of Ubuntu
Bug
*** This bug is a duplicate of bug 1736116 ***
https://bugs.launchpad.net/bugs/1736116
** This bug is no longer a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
** This bug has been marked a duplicate of bug 1736116
[SRU] Host
*** This bug is a duplicate of bug 1736116 ***
https://bugs.launchpad.net/bugs/1736116
** This bug is no longer a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
** This bug has been marked a duplicate of bug 1736116
[SRU] Host
*** This bug is a duplicate of bug 1745938 ***
https://bugs.launchpad.net/bugs/1745938
** This bug has been marked a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
--
You received this bug notification because you are a member o
I have tested kernel 4.13.0.38.57 from xenial-proposed and virtualbox is
still freezing with virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2.
Kernel 4.15.0.13.39, also from -proposed is too recent for Virtualbox
5.0.40-dfsg-0ubuntu1.16.04.2, and the vbox kernel module fails to build.
However, installing
*** This bug is a duplicate of bug 1745938 ***
https://bugs.launchpad.net/bugs/1745938
** This bug has been marked a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1745938 ***
https://bugs.launchpad.net/bugs/1745938
** This bug has been marked a duplicate of bug 1745938
System Freezes while starting VM in virtualbox after Kernrel Upgrade
4.13.0-31.34
--
You received this bug notification because you are a member o
I have the same issue and was able to reproduce it on both 4.13.0-21 and
4.13.0-25, as well as mainline 4.13.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745938
Title:
System Freezes while sta
I am also affected by this bug, Virtualbox modules won't build with
kernel 4.15, so I tried mainline kernel vmlinuz-4.13.16-041316-generic
and it was also affected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
As a workaround that doesn't require changing /etc/nsswitch.conf, you
can also explicitely disable sudo support for your sssd domain :
[sssd]
services = nss, pam, sudo
[mydomain/LDAP]
sudo_provider = none
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
*** This bug is a duplicate of bug 790863 ***
https://bugs.launchpad.net/bugs/790863
** This bug has been marked a duplicate of bug 790863
Unable to start lxc container after update to 2.6.32-32
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790542
Title:
network-enabled LXC containers not starting with linux-
image-2.6.32-32-generic (lucid)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Public bug reported:
Binary package hint: linux-image-2.6.32-32-generic
Trying to start LXC container yields the following result :
$ root@lxctest:~# lxc-start -n squeeze
lxc-start: failed to clone(0x6c02): Invalid argument
lxc-start: Invalid argument - failed to fork into a new namespace
lx
15 matches
Mail list logo
