Hi,
I've redeployed my test box with 14.04 with kilo-staging archive, but i
get a core dump when i try to run kvm the same way you did.
Can you show your /etc/apt/sources.list and /etc/apt/sources.list.d, as
well as output for
uname -a
dpkg -l | egrep -e '(qemu|linux|bios)'
--
You received
Indeed building the kilo package from source gives me the same hang. So
something else (seabios maybe)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64
I'll try building the package source from kilo on the xenial host and
see if that succeeds. I'm having doubts.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
Hm, building 2.2.0 (close to what is in the kilo cloud archive) doesn't
help.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image
Thanks very much for testing.
I think I have a system I can use to try and bisect tonight/tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64
Failing any brighter ideas, this should be pretty bisectable to figure
out what happened. Hardware availability is the main problem. Would
you be able to use your system to bisect to the commit introducing the
bug?
Actually before we get to that, could you try installing the 14.04 slof
package
Hi,
this should be fixed in libvirt 1.3.1-1ubuntu8. I'm not sure why it
didn't get auto-closed.
Please report if this is stlil broken for you.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Ok, so two things I've found are that
1. tcg emulated vms can't be migrated (this doesn't apply to you)
2. pc-1.0-qemu-kvm as the source machine type doesn't actually work. What
works for me is when i set the machine type to pc-1.0, then set
allow_incoming_qemukvm=1 in /etc/libvirt/qemu.conf
Just to be sure before I mark this as affecting upstream, could you
try adding more memory, maybe -m 1024?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
Could you try this using upstream qemu?
git clone http://git.qemu.org/git/qemu.git
cd qemu
sudo apt-get -y build-dep qemu
./configure --target-list=ppc64-softmmu
make
cd ppc64-softmmu
./qemu-system-ppc64 [...]
--
You received this bug notification because you are a member of Ubuntu
Server Team,
(Closed per discussion in the rh bug)
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/584862
Title:
libvirt
Hi,
looking at the information in the Description, it looks like you still
have /dev/nbd0 attached to the file you're using in qemu. Just to be
sure, does this still happen when you disconnect that first?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Description changed:
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
- ubuntu@alpine01:~$
Well this is unnerving. After re-installing the current versions of
qemu-kvm on the source host, it continues to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Ok, so reverting the qemu-kvm on the precise source host to 1.0+noroms-
0ubuntu14.18 seems to fix it. (And then using pc-1.0 machine type and
setting allow_incoming_qemukvm = 1 on the destination)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
+ [SRU Justification]
+ Impact: qemu stops processing traffic
+ Test case: see below (stress test using udp traffic generator)
+ Fix: cherrypick of upstream patch to fix this problem.
+
Description of problem:
- qemu socket becomes full, causing qemu to send
Actually even porting to trusty is complicated by a set of endianness
patches.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1556306
Title:
vhost-user: qemu stops processing
** No longer affects: qemu (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1493049
Title:
memory corruption during live-migration in TCG mode
To manage notifications
This is marked as affecting precise, but has anyone reproduced this with
qemu-kvm 1.0+noroms-0ubuntu14.27 ?
The patch is completely inapplicable to that code base, so it would need
to be rewritten from scratch if so.
** Changed in: qemu-kvm (Ubuntu Precise)
Status: New => Invalid
--
(if someone says they have reproduced it on 1.0+noroms-0ubuntu14.27 I'll
unmark it invalid.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1556306
Title:
vhost-user: qemu stops
I'm confused- this is marked as affecting qemu-kvm in precise, but the
preceding patch (c6ac36e) which introduced the bug is not there either.
So I'm going to mark this as not affecting precise unless someone speaks
up to say that we in fact need the whole dependent series.
** Changed in:
Hi,
just to be sure, if you run
kvm -vnc :1 -m 1.5G
kvm -vnc :1 -m 1.5G --no-hpet
do those also crash?
Can you please show the contents of
/var/log/libvirt/qemu/u1510-1.log
** Package changed: kvm (Ubuntu) => qemu (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
Assuming this is running upstart (as it looks like), try adding the
debug and verbose flags as shown in the upstart cookbook?
--
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/1551150
But unfortunately we do not know which patch fixed it, making an SRU
much more problematic. Someone who is able to reproduce the bug would
need to try to either bisect, or make educated guesses and test patch
cherrypicks.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: qemu (Ubuntu Vivid)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion hangs on large core
I'm afraid I've not yet made any headway.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Precise to Trusty live migration failing
To manage notifications about this
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Precise)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1558897
Title:
guest vm hangs
To manage notifications about
Quoting Vincent JARDIN (vincent.jar...@6wind.com):
> it seems that the fix was not applied on ppc build:
>
> https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-1ubuntu3/+build/8842754
>
> https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-1ubuntu3/+build/8842753
>
> neither on arm64:
Could you please show the result of
sudo systemctl
sudo systemctl status lxd
sudo systemctl status lxd.socket
dpkg -l | grep lxd
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Package changed: lxc (Ubuntu) => lxd (Ubuntu)
--
You received this bug notification because you are
Thanks for the confirmation.
A note for anyone else who runs into this - you will unfortunately need
to actually restart lxcfs, or reboot the host, for the fix to take.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
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/1560120
Title:
Unprivileged nested container will not start inside a
Christopher, thanks for reporting this. I've pushed the fix, but as
we're now in final freeze it may be delayed for approval.
** Changed in: lxcfs (Ubuntu)
Importance: Undecided => High
** Changed in: lxcfs (Ubuntu)
Status: New => Triaged
--
You received this bug notification
The proposed fix for this is https://github.com/lxc/lxcfs/pull/102
--
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/1560120
Title:
Unprivileged nested container will not start inside a
I believe this is due to lxcfs not implementing access(2).
** Also affects: lxcfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Confirmed, i can reproduce. Now why.
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
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/1560120
Title:
Unprivileged nested
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1560120
Title:
Unprivileged nested container will not start inside a
Hm,
lxc-start 20160321163436.552 ERROR lxc_utils - utils.c:mkdir_p:253 -
Permission denied - failed to create directory '/sys/fs/cgroup/blkio/lxc
/libertine-smoke-test/lxc/'
This is odd, if that was not writeable then cgfsng should not have
stored it as a writeable hierarchy.
Just to make
@Nish,
is there a particular bug in the package which this fixes, or is this
purely to have a closer package to debian's in 16.04?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
Thanks, the debdiff looks fine to me. Will sponsor this when the FFE is
approved.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1560148
Title:
[FFe] Please merge with openipmi
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1553023
Title:
[FFe] libvirt v1.3.2 -- zfs support
To
Thanks for reporting this bug. I'll push into the xenial package today.
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
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/1556447
Title:
lxc-start fails: lxc_cgfsng -
The EBUSY errors from lxc-init mounts are ok, it's because lxc has
already mounted those (by following the automatically included
configuration files).
i'd expect eperm for the /sys/kernel/debug mount, because you're not
allowed to read under /sys/kernel/debug. But strace shows that by hand
i
*** This bug is a duplicate of bug 1556306 ***
https://bugs.launchpad.net/bugs/1556306
** This bug has been marked a duplicate of bug 1556306
vhost-user: qemu stops processing packets under high load of traffic
--
You received this bug notification because you are a member of Ubuntu
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server
Seems likely. Thanks.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Fix Released
--
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/1557607
Title:
Xenial container fails to
Could you please show the container configuration?
--
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/1558565
Title:
Unprivileged system LXC containers refuse to start after upgrade to
Hi,
so just to be clear, is there any reason for this not to be marked a
duplicate of 1556306 (and that bug marked as also affecting qemu-kvm)?
The same patch should be applied for both?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hm, that's odd. Assuming your login uid is in fact design, you do have
write access to your systemd cgroup. Just for sanity, can you confirm
that lxc-start still fails with the same error messages?
Please do show your ppa listings, and current versions for lxc packages
dpkg -l | grep lxc
**
Hi,
I think this is a bug which has just been fixed in pam_lxcfs. Could you
please show:
pwd=/sys/fs/cgroup/systemd/`awk -F: '/systemd/ { print $3 }' /proc/self/cgroup`
echo $pwd
ls -ld $pwd
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Marking verification-done bc the pids cgroup problem is addressed. If
you continue to have a problem with the apparmor profile, please file a
new bug.
** Tags removed: verification-failed verification-needed
** Tags added: verification-done
--
You received this bug notification because you are
** Changed in: usbredir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to usbredir in Ubuntu.
https://bugs.launchpad.net/bugs/1556316
Title:
Sync usbredir 0.7.1-1 (main) from Debian unstable
Hi,
I looked over the debdiff. I *think* all i saw in the source was
bugfixes, except for the addition of
usbredirhost_set_buffered_output_size_cb(). I don't know whether that
constitutes 'new API', which is part of FFE.
--
You received this bug notification because you are a member of Ubuntu
Quoting Stephen Warren (swar...@wwwdotorg.org):
> Could you please expand on "Then re-chown your current systemd cgroup"?
> I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
> path I should chown.
The systemd cgroupfs is mounted under /sys/fs/cgroup/systemd. Your current
It should be fixed in qemu 1:2.5+dfsg-5ubuntu5
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1533728
Title:
Thanks, Stephen, culprit found. The systemd cgroup was yours - until
you did a sudo.
For now you can work around this by commenting out the libpam-cgfs line
from /etc/pam.d/common-session-noninteractive. Then re-chown your
current systemd cgroup to yourself or log back in.
I'm not yet sure
Do you know whether you are using lightdm? Can you show your
/etc/pamd.d/common-session file?
--
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/1556447
Title:
lxc-start fails: lxc_cgfsng
Did you say your *host* fails shortly after starting that container? In
what way does the host fail?
Commenting out the line in 02-openvpn-auto-tun.conf avoids the problem?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
This is fixed in 1.3.1-1ubuntu7
** Package changed: qemu (Ubuntu) => libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel
Hi James,
the kilo libvirt package (which I assume this is?) does indeed not have
a rule for qemu-dm, which does exist in xen-utils-4.4 in trusty (and
there is no xen-utils in kilo archive).
Note this bug is not valid against the xenial libvirt package, as there
is no qemu-dm binary in
Since this was installed as 14.04, and libvirt-bin is not installed
masked by default, I'll assume this was a remnant of a previous install?
This shouldn't prevent the package install from succeeding though.
Indeed if I mask libvirt-bin and then do a apt-get install --reinstall
libvirt-bin, the
I have a test package building in ppa:serge-hallyn/virt.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1554031
Title:
error: internal error: unable to execute QEMU command
ok, actually I think this is simply an error in virt-aa-helper.
apparmor's load_profile() should be being called before the blockcommit
begins, to add rw access to the base image. Which is why the rw rule is
there. But the 'deny' rule is for some reason still there.
--
You received this bug
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1521931
Title:
apparmor-profile-load returns 1 if
Hi Brendan,
thanks for submitting this bug. Can you still reproduce this with 15.10
or 16.04? If so, can you give us a URL for the iso for semplice 7?
Do other guests also do this?
I assume you are running xrandr in the guest, not the host?
--
You received this bug notification because you
strace shows:
5082
open("/var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS5jbG91ZDpzZXJ2ZXI6MTYuMDQ6YW1kNjQgMjAxNjAxMjU=",
O_RDWR|O_CLOEXEC) = -1 EACCES (Permission denied)
The apparmor profile (libvirt-uuid.files) includes:
So the error message itself comes from qemu, in block/raw-posix.c:
error_setg_errno(errp, errno, "Could not reopen file")
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1554031
Title:
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1554031
Title:
** Changed in: qemu (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1554031
Title:
error: internal error: unable to execute QEMU command
Thanks for the update. Marked the bug "invalid" meaning "we have lost
the machine which could reproduce"
** Changed in: qemu (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1541810
Title:
libvirt-bin.service does not read
Hi,
could you please show the contents of
/etc/apparmor.d/libvirt/libvirt-99917005-9251-4ea3-9e72-946b42061df1 ?
virt-aa-helper *is* supposed to be adding an rw entry for each usb file
for hostdevs being added (through file_iterate_hostdev_cb()), so I'm
wondering which file isn't being handled
The default security driver in Ubuntu is apparmor.
Could you please show the output of
cat /etc/*-release
ls -l /etc/apt/sources.list.d
cat /etc/apt/sources.list.d/*
dpkg -l | egrep -e '(libvirt|qemu)'
and show any relevant DENIED messages in syslog (grep DENIED
/var/log/syslog)
Your libvirt
Fix for that one is building in xenial-proposed as well.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Thanks, @Dadio, I'll cherrypick the patch unless #qemu points to
objections.
** Package changed: libvirt (Ubuntu) => qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
this should be fixed by the fix to bug 1554269.
--
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/1543697
Title:
Unprivileged nested Xenial container will not start inside a
privileged
Hi - there should be a way, we just need to get sudo running the pam
module.
Perhaps libpam-cgfs should be added to /etc/pam.d/common-session-
noninteractive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Quoting Christopher Townsend (christopher.towns...@canonical.com):
> I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
> didn't know this existed. However, it didn't help.
>
> As you say, I can create unprivileged containers as user ubuntu, I just
> can't start them. Are
I'm running 4.4.0-10-generic #25-Ubuntu with lxc version
2.0.0~rc5-0ubuntu1 , and the privileged container has:
lxc.include = /usr/share/lxc/config/nesting.conf
in the configuration file. This is a clean VM with no ppas installed.
Inside the privileged container (also xenial with no ppas), I
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
> The patches were just sent upstream.
>
> http://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg00057.html
Thanks. The feedback also seems generally good, so I'm comfortable
with this. The main problem now is timing, since we are well past
feature freeze for 16.04. So if we want this in
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 Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
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 Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Current wily kernel is giving me the same behavior.
--
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/1543367
Title:
nested unprileged container fails to start at mounting /proc
To
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
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
Hi,
I'm having a problem as well, but a different one in recent xenial
kernels.
Can you tell us the release and kernel (uname -a) of your host?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
As I understand the code to work, it should do exactly what pitti wants.
Those fds which were not redirected should get a pty allocated, so in
your example you should in fact see stderr output.
So I think this is a bug and no new flag should be needed.
--
You received this bug notification
Please show which version you are currently using?
--
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/1543697
Title:
Unprivileged nested Xenial container will not start inside a
A fix for this has been sent upstream. A new rc will be released very
soon with the fix.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
There are two problems.
First is that cgfs is not falling back to $container-1 when $container
cgroup is not available for reuse.
Second is that cgroups are not being cleaned up on container shutdown.
lxcfs will need to prune those by hand either at shutdown or startup.
Doing so at shutdown is
Actually in my case it actually segfaults
--
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/1552355
Title:
Unprivileged lxc will not start after being stopped
To manage notifications
I can reproduce that here on my laptop.
status confirmed
importance high
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
/self/cgroup, or simply always mount it.
** Affects: cgroup-lite (Ubuntu)
Importance: High
Assignee: Serge Hallyn (serge-hallyn)
Status: Triaged
** Changed in: cgroup-lite (Ubuntu)
Importance: Undecided => High
** Changed in: cgroup-lite (Ubuntu)
Status: New => T
Hi,
sorry, mountinfo does not show the hierarchies. Can you show
/proc/cgroups and /proc/self/cgroup output?
--
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/1551150
Title:
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1546445
** No longer affects: libvirt (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1524737
Title:
systemd presents hugetblfs at /dev/hugepages
To manage notifications
Confirmed this has regressed in xenial
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt
1 - 100 of 6035 matches
Mail list logo
