Public bug reported:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pools, then verifies that writes
happened as expected.
On 16.04 physical host it
apport information
** Tags added: apport-collected zesty
** Description changed:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pool
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998182/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998183/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998185/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998184/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998189/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998187/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998186/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998188/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998190/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998192/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998191/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998194/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998193/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109
http://pastebin.com/raw/YPGG6usG is the reproduction script.
In virtualbox it actually passes. Maybe this really is a problem with
the disk driver for vmware?
** Description changed:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The
Well, actually on virtualbox it's touch-and-go.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109
Title:
nbd (
*** This bug is a duplicate of bug 1628336 ***
https://bugs.launchpad.net/bugs/1628336
** This bug has been marked a duplicate of bug 1628336
mount-image-callback cannot mount partitioned disk image
--
You received this bug notification because you are a member of Kernel
Packages, which i
Nope, tail -f is still broken at least in 4.12.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in coreutil
I've seen reports that this is fixed in 4.10?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in coreutils
@sforshee - are you saying that removing the debugfs line from
/usr/share/lxc/config/ubuntu-common.conf fixes this for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854
Title:
@sforshee,
Because in the past mountall would fail if we didn't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854
Title:
LXD bootstrap issues on xenial
Status in linux package in
Note - I am not actively looking at this bug as I've not managed to
reproduce it. Hopefully the kernel team has it under control, please
shout if I'm needed.
If using juju first is a prerequisite to reproducing this, I can try
that, but my impression from previous reports has been that this is no
Upstream kernel still fails:
lxc-start 20160304193125.498 ERRORlxc_conf -
conf.c:lxc_mount_auto_mounts:742 - Operation not permitted - error mounting
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
lxc-start: conf.c: lxc_mount_auto_mounts: 742 Operation not permitted - error
mount
Current wily kernel is giving me the same behavior.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367
Title:
nested unprileged container fails to start at mounting /proc
Status in
Simplest way to reproduce:
sudo systemctl stop proc-sys-fs-binfmt_misc.automount # (just to be sure)
unshare -mpf
mount --make-rslave /
mount -t proc proc /proc
lxc-usernsexec
# mount -t proc proc /proc # permission denied, regardless what -o options may
pass.
--
You received this bug notificat
Sorry, testcase in #8 is invalid, bc lxc-usernsexec doesn't create a new
pid namespace, so mount is denied because we do not own our
pidns->userns.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Ok, this is happening because lxc, for privileged containers, bind-
mounts /proc/sys and /proc/sys/net onto themselves. This prevents later
unprivileged mounting of /proc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Sorry, I had forgotten my own workaround for this.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification beca
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558897
Title:
guest vm hangs
Status in linux package in Ubunt
Hm - I can boot a wily cloud image, just not a xenial one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=my-seed.img,if=virtio
** Attachment added: "crash.png"
https://bugs.launchpad.ne
Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I
can boot the installed image (with same kernel) just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
4.4.0-16 also works.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64
If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know. Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do boot.
@leftyfb - what exactly is IBM asking to verify? Whether kvm works
under powervm? Did smoser's info help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc6
Public bug reported:
Cgroup namespaces are a new kernel feature which allows virtualizing a
container's /proc/self/cgroups and the root of future cgroupfs mounts,
to make the container appear as though it is in the / cgroup. This is
one of the pieces needed to be able to run, for instance, docker
I get no warnings with 4.2.0-29-generic #34-Ubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349
Title:
sleep from invalid context in aa_move_mount
Status in linux package in
Wait, that's not a valid test is it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349
Title:
sleep from invalid context in aa_move_mount
Status in linux package in Ubuntu:
Fix R
Well, that's wily-proposed, so +1
** Tags removed: verification-needed-wily
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349
Title:
sleep from inv
marking confirmed because two people have reported it, but I cannot
reproduce it yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854
Title:
LXD bootstrap issues on xenial
Statu
I'm on the same kernel
Linux sl 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
and also have the tracefs mounted
0 ✓ serge@sl ~ $ grep debug /proc/self/mountinfo
74 19 0:7 / /sys/kernel/debug rw,relatime shared:26 - debugfs debugfs rw
44 74 0:9 / /sys/
Also cannot reproduce in a clean VM, so I have to assume juju is
tweaking something.
Can you show output of 'lxc config show ' where
is the container which fails?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** Changed in: cgmanager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Pa
Public bug reported:
In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
the following policy:
#include
/home/ubuntu/mount {
#include
#include
capability,
network,
mount,
/** mkrwixr,
}
And then run the following script under sudo from ~/ubuntu:
#!/bin/sh
app
Public bug reported:
Create a trusty or xenial host. Probably use ubuntu-lxc/daily ppa to
work around other bugs.
Create a privileged container (again either trusty or xenial will do),
and install ubuntu-lxc/daily ppa there.
Create an unprivileged container in that container. It will fail at
m
I'm quite certain this is not an apparmor issue, since leaving
everything unconfined does not help.
It could be something we're doing wrong in lxc, but I'm not sure what.
It could be something inherent in mounting onto an open fd.
--
You received this bug notification because you are a member o
Note that an unprivileged user on the host is able to do these mounts.
Unprivileged users inside a privileged container cannot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367
Titl
It's not something I regularly do, as I normally nest inside unprivileged
lxd containers. So I can't say whether it is a regression. I did revert
to an older trusty kernel and have the same behavior.
I'm going to need to write a script to make this more easily reproducible,
but I won't have time
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-meta-lts-vivid (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
(Where the last prompt comes from the lxc-attach having been killed)
stopping lxcfs on the host prevents this from happening.
I don't think lxcfs is to blame, though but rather fuse.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificat
An strace of the attach shows:
15047 read(0,
15047 +++ killed by SIGKILL +++
15033 <... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL}], 0,
NULL) = 15047
15033 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=15047,
si_uid=0, si_status=SIGKILL, si_utime=2, si_stime=1} ---
No - this being moot does not apply to wily.
Actually the xenial work has been delayed so it does not *yet* apply
there either.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1392176
Titl
@Sqxm - thanks for that input.
For what it's worth you should be able to use ppa:serge-hallyn/systemd
in xenial to get cpusets not created by default. Unfortunately I need
to make some more changes (in particular to use the systemd-created
cgroups when they exist) before pushing this to the archi
Quoting Shimin (shi...@databricks.com):
> Thanks for looking into it. Are there any downsides to disabling udev in
> the container (by removing /etc/init/udev.conf for example) if we don't
> need the container to be notified of new devices?
hi, no this should have no downsides. You can just
echo
summary overlay: mkdir in user namespace fails if directory exists in
lowerdir"
** Description changed:
If a directory exists in the lowerdir but not in the mounted
overlay, then mkdir of the directory in the target dir results
in a mysterious -EPERM. I've seen this both in wily kernel
Quoting Joseph Salisbury (joseph.salisb...@canonical.com):
> Can you see if this bug also happens with the latest mainline kernel? It can
> be downloaded from:
That is not an option, because the mainline kernel doesn't support unprivileged
overlayfs mounting which is where this happens.
--
You
In ovl_create_over_whiteout(), the ovl_set_opaque() in the S_ISDIR()
block failed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747
Title:
overlay: mkdir fails if directory exists
The type of the underlaying file does not matter, only the type of the
replacing object.
So if you
touch $t/dev; rm $t/dev; touch $t/dev
mkdir $t/dev; rmdir $t/ev; touch $t/dev
those succeed, while
touch $t/dev; rm $t/dev; mkdir $t/dev
mkdir $t/dev; rm $t/dev; mkdir $t/dev
both fail.
--
You
Ok, I see. At one point we had a special case to allow the overlay code
to write trusted.* xattrs for creating whiteouts.
However that is gone. Therefore when overlayfs v1 (mount -t overlayfs)
is mounted, root in a user namespace also is not able to rm a file which
exists in the lower fs.
Some
#2 is probably a bit too gross - we really only need the cap for the setting
of the OVL_XATTR_OPAQUE xattr in ovl_set_opaque. So we could simply override
creds again there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
hat may not be ok for the ovl_rename2 case.
What we want is for inode permissions to be checked, but only the
bit in xattr_permission() checking for trusted.* to accept ns_capable.
We could special-case that in xattr_permission(), but that's not
particularly nice.
--
You received this bug notif
Quoting Seth Forshee (seth.forshee...@canonical.com):
> I don't know why #2 is that much grosser than what's there now. It's
I didn't mean gross as in eeuw, I meant not fine-grained enough.
Because the capability will apply to inode permissions checks,
and we only want it to be used for the check
in ovl_clear_empty(), the opaque bit is set on the dir in workingdir
in ovl_create_over_whiteout() (the case we're currently looking at) it is
also being set in the working dir.
in ovl_rename2(), it is set in two places, on the upper dentries for
both the old and new.
So it is never set on the l
Does it require the workdir to be empty?
I.e. is there a way (symlink, bind mount, something else) that a user
could use a dir they own which has a child which they don't own?
It looks like no, since
root@w1:/tmp# mount -t overlay -o lowerdir=lower,upperdir=upper,workdir=workdir
overlay /mnt
ro
> Something I'm still not sure about is what would happen if you made a
> symlink, bind mount, etc. in upperdir with the same name as an unrelated
> file in lowerdir. This is worth checking out.
just tried a symlink and it didn't seem to affect the host directory
(/opt/cisco) which was symlinked t
marking as affecting kernel given the description.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536280
Titl
Thanks for reporting this bug. The 'kvm' package shouldn't really exist.
The bug you're referring to is in the kernel kvm code, so I'm marking it
as affecting the kernel. (If it were in the userspace qemu package, then
the 'qemu' package would be the right bug target).
** Package changed: kvm (Ubu
Thanks for reporting this bug. The 'kvm' package shouldn't really
exist. The bug you're referring to is in the kernel kvm code, so I'm
marking it as affecting the kernel. (If it were in the userspace qemu
package, then the 'qemu' package would be the right bug target).
** Package changed: kvm (
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Invalid
** No longer affects: lxc (Ubuntu Vivid)
** No longer affects: lxc (Ubuntu Wily)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Thanks - both of those seem to suggest there is a bug in the virtio
driver in the guest kernel. Are the guests in both cases on the
same release and same kernel?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Summary changed:
- kvm vm loses network connectivity under "enough" load
+ kvm virtio netdevs lose network connectivity under "enough" load
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which
There has also been some concern about the propriety of the
proposed fix (when a newer kernel with the upstream fixes should
appear), in addition to lack of verifiaction - so please go ahead
and supersede this if you haven't already.
--
You received this bug notification because you are a member
Unfortunaty the check is not a simple uid comparison, because when I
use lxc-usernsexec to cat the file using the uid of root in the container,
I still get EPERM.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Expanding on comment #4: Otherwise we could work around it more easily
in lxc. As it is, if we can't cleanly/safely allow it in the kernel, we
may need to ask a new lxc command interface query to get the container's
personality.
--
You received this bug notification because you are a member of K
Oh, yeah, I forgot we had that. That sounds good.
Far preferable to having to tweak/relax the kernel constraints on reading
that file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13220
Thanks for reporting this bug. Given the lkml.org fix, I assume this is
in fact a kernel bug, so assigning it as such.
This is presumably fix-released in utopic, but SRU-able to precise and
trusty's backport kernels. I'm not clearn on how that process works, so
leaving it like this.
** Also aff
Thanks, given that info it seems clear to be a kernel and not a qemu
bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virt-manager (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
(Removed the task against virt-manager since hyperv is apparently *not*
a safe workaround in all cases)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes
Thanks, the soft lockup message in that dmesg may be helpful. Marking
as affecting the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
** Changed in: pm-utils (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/907188
Tit
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218959
Title:
KVM virbr# no longer forwards multicast traffic
I had thought that we'd need a udev rule to work around this, but
looking over the fedora bug in more detail it looks like cherrypicking
the two patches mentioned in comment 31 (
https://bugzilla.redhat.com/show_bug.cgi?id=880035#c31 ) should do it.
Can those who are suffering from this bug please
** Description changed:
A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS
(approx June-Aug 2013) and has stopped the (default) behaviour of
automatically forwarding multicast traffic over virbr#. Some updates
the bridge subsystem now, by default, disable multicast traffi
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307829
Title:
network namespace error
Status in “iproute” pac
So the particular files /var/run/netns/whatzit are bind-mounted
/proc/self/ns/net files from a task which no longer exists, which are
pinning the netns.
Interestingly, if I reproduce this by hand by doing
term 1: lxc-unshare -s NETWORK -- /bin/bash
term 2: mkdir /var/run/netns/z; mount --bind /p
Ok I see the problem but am not sure what to do about it.
iproute makes /var/run/netns MS_SHARED. When a container starts up, it
umounts everything. So the netns bind mounts are being umounted on the
host.
Ideally it woudl be as simple as marking /var/run/netns MS_SLAVE before
spawnign the cont
Public bug reported:
CONFIG_MEMCG_KMEM is disabled in the trusty kernel. It's the
recommended way to prevent forkbombs, so if there's not a good reason to
have it disabled, it would be great if that could be changed.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Tim Gardne
Thanks, Barry. So IIUC this has nothing to do with qemu, so I'm
switching it to linux.
Is it safe to assume that other VMs - other Ubuntu releases, or other
distros, or windows, do not have this behavior?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Thanks for reporting this bug. Just to be clear - is the laptop in fact
'suspending' or 'hibernating'? Do you have this same problem if you
remove the custom configuration for hybrid suspend?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pm-utils (Ub
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/997711
Title:
on resume no login screen
Status in “linux” pack
Thanks, that is a great reproducer.
Note that doing
rm -rf /etc/ssl/private
mkdir /etc/ssl/private
works around this, and explains why this *may* in fact be on purpose. If you
only do
sudo chown ubuntu:ubuntu /etc/ssl/private
then the underlying directory is still owned by root and n
@Tim,
is rmdir/mkdir an acceptable workaround for juju (ie can we lower
priority of the bug) or will that not be doable?
** Changed in: lxc
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/629117
Title:
Suspend failing on Dell Latitude E4310
Status in The Dell
Please reply if this is still an issue on a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Status: New => Invalid
** Changed in: pm-utils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Package
** Changed in: lxc (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Kernel
Packages, whic
Quoting Seth Forshee (seth.forshee...@canonical.com):
> I tried the kernel patch from the mailing list, but that doesn't fix the
> problem. It does fix permissions for most /proc/pid/* files in setuid
> processes, but the console problems remain.
That's interesting! Thanks for testing.
--
You r
Quoting Seth Forshee (seth.forshee...@canonical.com):
> stderr actually is mapped to a pty. The problem seems to be that getty
> can't set /dev/console as its controlling terminal because it's already
> the controlling tty for init, which is in a different process group.
> Thus getty ends up with n
1 - 100 of 300 matches
Mail list logo
