[Bug 1811087] Re: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary
Hm, I just figured out that I missed the last really useful comment because I did not get an e-mail about it. Anyway, https://github.com/lxc/lxc/issues/3186 now explains in more detail how to quickly build fuidshift from source. Thank you, Stéphane! ** Bug watch added: LXC bug tracker #3186 https://github.com/lxc/lxc/issues/3186 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811087 Title: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1811087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851113] [NEW] equivs-build fails to create DEB package w/o reporting an error
Public bug reported: I used equivs in the past to build meta packages to ensure that certain packages are installed on my systems. This always worked well. With the Ubuntu 19.10, I am unable to build any meta package with equivs even though the program does not report any error. Running "equivs-build control" in ~/build using the attached demo control file results in the following output: dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'test-deb' in '../test-deb_1_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! However, no DEB package is created at all. Neither in the ~/ nor in ~/build nor anywhere else. ** Affects: equivs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Demo control file" https://bugs.launchpad.net/bugs/1851113/+attachment/5302427/+files/control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851113 Title: equivs-build fails to create DEB package w/o reporting an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1851113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811087] [NEW] [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary
Public bug reported: lxd-tools used to ship the fuidshift command which is useful for shifting UIDs and GIDs of the container root filesystem in order to convert privileged into unprivileged containers. lxd-tools is now a meta package that will enforce that the lxd snap package is being installed. However, lxd snap (tested: stable channel, version 3.0.3 and 3.9) does not seem to provide fuidshift. To get fuidshift back, I had to forcibly install an older version of lxd-tools: https://ubuntu.pkgs.org/18.04/ubuntu-updates-universe-amd64 /lxd-tools_3.0.3-0ubuntu1~18.04.1_amd64.deb.html Being a replacement also for lxd-tools, lxd snap should ship all binaries that used to be shipped. ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Tags: fuidshift lxd missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811087 Title: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1811087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635029] Re: apt-cacher-ng in yakkety lacks distkill.pl
Thanks again Eduard, for submitting the improvement proposal to the project's todo list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635029 Title: apt-cacher-ng in yakkety lacks distkill.pl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1635029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635029] Re: apt-cacher-ng in yakkety lacks distkill.pl
Thanks Eduard! Based on your hint, I was able to figure out what needs to be done: 1. Open http://:3142/acng-report.html in the browser 2. Click "Start Scan and/or Expiration" button 3. Wait for the scan to finish 4. After the scan has finished, navigate to "Allocated disk space (Top 10, show more / cleanup)" at the bottom of the page and click the link "show more / cleanup" 5. Select the check boxes left to all listed release files, we want to get rid of (seems to put a lot of load on my Firefox as checking the boxes and scrolling made the browser freeze a lot) 6. At the bottom of the page, click the button "Delete selected files" 7. On the next page, click the button "Delete files" So it is not the apt-cacher-ng package that has a bug, but the documentation on the German Ubuntu wiki that is outdated. Unfortunately, the procedure above is not really straight forward. Even in case that you have already navigated to the apt-cacher-ng browser page. It is not really intuitive that you have to click the tiny link "show more / cleanup" in order to start making all the old distro killing happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635029 Title: apt-cacher-ng in yakkety lacks distkill.pl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1635029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635029] [NEW] apt-cacher-ng in yakkety lacks distkill.pl
Public bug reported: /usr/lib/apt-cacher-ng/distkill.pl is missing! As mentioned here https://www.unix-ag.uni-kl.de/~bloch/acng/html/maint.html#distkill and also here https://wiki.ubuntuusers.de/Lokale_Paketquellen/Apt-Cacher-ng/#Distkill this script is needed to get rid of the DEB files of older distros for which packages should not be cached anymore. I remember having used this script in the past, but with yakkety it seems to have vanished. Even reinstall of the apt-cacher-ng package didn't bring it back. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt-cacher-ng (not installed) ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 19 21:59:58 2016 SourcePackage: apt-cacher-ng UpgradeStatus: Upgraded to yakkety on 2016-02-06 (256 days ago) ** Affects: apt-cacher-ng (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug distkill.pl yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635029 Title: apt-cacher-ng in yakkety lacks distkill.pl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1635029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559317] [NEW] [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt
Public bug reported: Using virt-manager and libvirtd, I added a VirtFS filesystem passthrough to an existing qemu virtual machine also running Ubuntu. The XML code generated by libvirt looks like this: Inside the VM, I am able to mount the filesystem passthrough like this: mount -t 9p -o trans=virtio,version=9p2000.L,rw p9_mapped /mnt After mounting, it is possible to read the contents of the passthrough, but it is not possible to write into the directory. E.g. 'touch /mnt/test' results in the error: touch: cannot touch ‘/mnt/test’: Permission denied Using the other p9 access modes 'passthrough' and 'squash' also does not work. Read is possible, write isn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libvirt-bin 1.3.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 18 22:12:34 2016 SourcePackage: libvirt UpgradeStatus: Upgraded to xenial on 2016-02-06 (41 days ago) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/libvirt/qemu/networks/default.xml'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug libvirt p9 qemu xenial ** Tags added: libvirt p9 qemu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559317 Title: [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1559317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559317] Re: [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt
** Tags removed: p9 ** Tags added: 9p ** Summary changed: - [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt + [xenial] No write access to VirtFS (9p) in qemu VM run by libvirt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559317 Title: [xenial] No write access to VirtFS (9p) in qemu VM run by libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1559317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559317] [NEW] [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt
Public bug reported: Using virt-manager and libvirtd, I added a VirtFS filesystem passthrough to an existing qemu virtual machine also running Ubuntu. The XML code generated by libvirt looks like this: Inside the VM, I am able to mount the filesystem passthrough like this: mount -t 9p -o trans=virtio,version=9p2000.L,rw p9_mapped /mnt After mounting, it is possible to read the contents of the passthrough, but it is not possible to write into the directory. E.g. 'touch /mnt/test' results in the error: touch: cannot touch ‘/mnt/test’: Permission denied Using the other p9 access modes 'passthrough' and 'squash' also does not work. Read is possible, write isn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libvirt-bin 1.3.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 18 22:12:34 2016 SourcePackage: libvirt UpgradeStatus: Upgraded to xenial on 2016-02-06 (41 days ago) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/libvirt/qemu/networks/default.xml'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug libvirt p9 qemu xenial ** Tags added: libvirt p9 qemu -- 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/1559317 Title: [xenial] No write access to VirtFS (p9) in qemu VM run by libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1559317/+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
[Bug 1494447] Re: Amule/Amule Adunanza do not open on Wily
*** This bug is a duplicate of bug 1486000 *** https://bugs.launchpad.net/bugs/1486000 ** This bug has been marked a duplicate of bug 1486000 amule crashed with SIGABRT in wxVLogFatalError() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494447 Title: Amule/Amule Adunanza do not open on Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amule/+bug/1494447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455809] Re: [vivid] Ubuntu session crashes on LDAP login via SSSD
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455809 Title: [vivid] Ubuntu session crashes on LDAP login via SSSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1455809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455809] Re: [vivid] Ubuntu session crashes on LDAP login via SSSD
Sorry, for an unknown reason, a wrong package was selected when I submitted the bug. I think that the bug affects the Ubuntu standard session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455809 Title: [vivid] Ubuntu session crashes on LDAP login via SSSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1455809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455809] [NEW] [vivid] Ubuntu session crashes on LDAP login via SSSD
Public bug reported: Following situation: - Ubuntu is configured use SSSD to permit login of LDAP users - Automatic creation of home directories is switched on and confirmed to work - LDAP users (as well as local users) can login to * local console * SSH console * LXDE (via LightDM) * Openbox (via LightDM) - However, LDAP users can't use the standard Ubuntu session (Unity) because it crashes right after LightDM permits the login (returning to the LightDM greeter) - Local users can login to the standard Ubuntu session without any problems - For LDAP users, after each failed login attempt, a file like upstart-udev-bridge.21334.pid containing a five digit number different from that in the file name is left back in the home directory ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Attachment added: Relevant section of lightdm.log https://bugs.launchpad.net/bugs/1455809/+attachment/4398635/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455809 Title: [vivid] Ubuntu session crashes on LDAP login via SSSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1455809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455809] Re: [vivid] Ubuntu session crashes on LDAP login via SSSD
** Attachment added: Relevant section of auth.log https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1455809/+attachment/4398636/+files/auth.log ** Package changed: sddm (Ubuntu) = gnome-session (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455809 Title: [vivid] Ubuntu session crashes on LDAP login via SSSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1455809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445611] Re: [vivid] lxc container with systemd fails to boot under libvirt-lxc
Thank you for pointing this out. Based on your reply, I decided to have the host system boot on /bin/systemd and have the containers boot on /sbin/upstart. So far, this works without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445611 Title: [vivid] lxc container with systemd fails to boot under libvirt-lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1445611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445611] Re: [vivid] lxc container with systemd fails to boot under libvirt-lxc
The container can be booted via lxc-start using the attached config. The container can also be booted using libvirt-lxc as long as it is configured to use /sbin/upstart as init. However, when configured to boot on /bin/systemd, it still fails as reported above. Is anyone else experiencing this problem? ** Attachment added: config https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1445611/+attachment/4386998/+files/config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445611 Title: [vivid] lxc container with systemd fails to boot under libvirt-lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1445611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445611] [NEW] [vivid] lxc container with systemd fails to boot under libvirt-lxc
Public bug reported: Under vivid, a vivid container fails to boot with systemd, printing the following error message in console: Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization 'lxc-libvirt'. Detected architecture 'x86-64'. Welcome to Ubuntu Vivid Vervet (development branch)! Set hostname to test. Failed to install release agent, ignoring: No such file or directory Failed to create root cgroup hierarchy: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. On the host, the following dmesg is found: [ 805.407722] audit: type=1400 audit(1429295378.619:150): apparmor=STATUS operation=profile_load profile=unconfined name=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e pid=3796 comm=apparmor_parser [ 805.431061] device vnet0 entered promiscuous mode [ 805.446988] IPv6: ADDRCONF(NETDEV_UP): vnet0: link is not ready [ 806.043772] eth0: renamed from vnet1 [ 806.067844] IPv6: ADDRCONF(NETDEV_CHANGE): vnet0: link becomes ready [ 806.067942] virbr0: port 2(vnet0) entered listening state [ 806.067959] virbr0: port 2(vnet0) entered listening state [ 806.096686] audit: type=1400 audit(1429295379.307:151): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/systemd/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.096914] audit: type=1400 audit(1429295379.307:152): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/systemd/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098253] audit: type=1400 audit(1429295379.307:153): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/freezer/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098474] audit: type=1400 audit(1429295379.307:154): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/net_cls,net_prio/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098640] audit: type=1400 audit(1429295379.307:155): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/devices/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098805] audit: type=1400 audit(1429295379.307:156): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/cpu,cpuacct/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098978] audit: type=1400 audit(1429295379.307:157): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/blkio/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.099149] audit: type=1400 audit(1429295379.307:158): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/cpuset/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 808.073724] virbr0: port 2(vnet0) entered learning state [ 810.079825] virbr0: topology change detected, propagating [ 810.079854] virbr0: port 2(vnet0) entered forwarding state To reproduce the bug, do the following (libvirt XML file is attached): $ lxc-create -P /lxc -n test -t download -B btrfs -- --dist=ubuntu --release=vivid --arch=amd64 $ virsh -c lxc:/// define test.xml $ virsh -c lxc:/// start test Then use e.g. virt-manager to view the console output. Package versions: apparmor = 2.9.1-0ubuntu9 cgmanager = 0.36-2ubuntu5 libvirt-bin = 1.2.12-0ubuntu12 lxc = 1.1.2-0ubuntu3 lxcfs = 0.7-0ubuntu2 systemd = 219-7ubuntu2 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt lxc systemd vivid ** Attachment added: libvirt XML file of the vivid lxc container https://bugs.launchpad.net/bugs/1445611/+attachment/4378622/+files/test.xml ** Package changed: lxc (Ubuntu) = libvirt (Ubuntu) -- 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/1445611 Title: [vivid] lxc container with systemd fails to boot under libvirt-lxc To manage notifications about this bug go to:
[Bug 1445611] [NEW] [vivid] lxc container with systemd fails to boot under libvirt-lxc
Public bug reported: Under vivid, a vivid container fails to boot with systemd, printing the following error message in console: Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization 'lxc-libvirt'. Detected architecture 'x86-64'. Welcome to Ubuntu Vivid Vervet (development branch)! Set hostname to test. Failed to install release agent, ignoring: No such file or directory Failed to create root cgroup hierarchy: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. On the host, the following dmesg is found: [ 805.407722] audit: type=1400 audit(1429295378.619:150): apparmor=STATUS operation=profile_load profile=unconfined name=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e pid=3796 comm=apparmor_parser [ 805.431061] device vnet0 entered promiscuous mode [ 805.446988] IPv6: ADDRCONF(NETDEV_UP): vnet0: link is not ready [ 806.043772] eth0: renamed from vnet1 [ 806.067844] IPv6: ADDRCONF(NETDEV_CHANGE): vnet0: link becomes ready [ 806.067942] virbr0: port 2(vnet0) entered listening state [ 806.067959] virbr0: port 2(vnet0) entered listening state [ 806.096686] audit: type=1400 audit(1429295379.307:151): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/systemd/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.096914] audit: type=1400 audit(1429295379.307:152): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/systemd/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098253] audit: type=1400 audit(1429295379.307:153): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/freezer/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098474] audit: type=1400 audit(1429295379.307:154): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/net_cls,net_prio/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098640] audit: type=1400 audit(1429295379.307:155): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/devices/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098805] audit: type=1400 audit(1429295379.307:156): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/cpu,cpuacct/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.098978] audit: type=1400 audit(1429295379.307:157): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/blkio/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 806.099149] audit: type=1400 audit(1429295379.307:158): apparmor=DENIED operation=mount info=failed type match error=-13 profile=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e name=/sys/fs/cgroup/cpuset/ pid=3834 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec [ 808.073724] virbr0: port 2(vnet0) entered learning state [ 810.079825] virbr0: topology change detected, propagating [ 810.079854] virbr0: port 2(vnet0) entered forwarding state To reproduce the bug, do the following (libvirt XML file is attached): $ lxc-create -P /lxc -n test -t download -B btrfs -- --dist=ubuntu --release=vivid --arch=amd64 $ virsh -c lxc:/// define test.xml $ virsh -c lxc:/// start test Then use e.g. virt-manager to view the console output. Package versions: apparmor = 2.9.1-0ubuntu9 cgmanager = 0.36-2ubuntu5 libvirt-bin = 1.2.12-0ubuntu12 lxc = 1.1.2-0ubuntu3 lxcfs = 0.7-0ubuntu2 systemd = 219-7ubuntu2 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt lxc systemd vivid ** Attachment added: libvirt XML file of the vivid lxc container https://bugs.launchpad.net/bugs/1445611/+attachment/4378622/+files/test.xml ** Package changed: lxc (Ubuntu) = libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445611 Title: [vivid] lxc container with systemd fails to boot under libvirt-lxc To manage notifications about this bug go to:
[Bug 1432644] Re: VM permanently tries to read /dev/shm/lttng-ust-wait-5
This is the XML (virsh -c lxc:/// dumpxml test): domain type='lxc' nametest/name uuid9d578815-a1e9-4596-aef9-a70717574f0e/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'2/vcpu resource partition/machine/partition /resource os type arch='x86_64'exe/type init/sbin/init/init /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' accessmode='passthrough' source dir='/lxc/test/rootfs'/ target dir='/'/ /filesystem interface type='bridge' mac address='00:16:00:69:5b:88'/ source bridge='virbr0'/ guest dev='eth0' actual='vnet1'/ /interface console type='pty' target type='lxc' port='0'/ /console /devices /domain -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432644 Title: VM permanently tries to read /dev/shm/lttng-ust-wait-5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432644] Re: VM permanently tries to read /dev/shm/lttng-ust-wait-5
With libvirt 1.2.12-0ubuntu8 being installed, virsh still fails to start an LXC operating system container, resulting in the following dmesg: [ 126.832553] audit: type=1400 audit(1427571328.167:150): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=4285 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 126.832646] audit: type=1400 audit(1427571328.167:151): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=4285 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 127.195264] audit: type=1400 audit(1427571328.527:152): apparmor=STATUS operation=profile_remove profile=unconfined name=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e pid=4310 comm=apparmor_parser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432644 Title: VM permanently tries to read /dev/shm/lttng-ust-wait-5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434999] Re: Creating a new VM in virt-manager fails because of apparmor permissions
It seems as if /etc/apparmor.d/abstractions/libvirt-lxc is also missing at least one necessary entry. In current Vivid, $ virsh -c lxc:/// start test fails, resulting in the following dmesg: [ 2207.856469] audit: type=1400 audit(1427382800.914:235): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=6827 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 2207.856521] audit: type=1400 audit(1427382800.914:236): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=6827 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 2208.101311] audit: type=1400 audit(1427382801.158:237): apparmor=STATUS operation=profile_load profile=unconfined name=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e pid=6828 comm=apparmor_parser [ 2208.123112] device vnet2 entered promiscuous mode [ 2208.490910] virbr0: port 2(vnet2) entered disabled state [ 2208.492774] device vnet2 left promiscuous mode [ 2208.492789] virbr0: port 2(vnet2) entered disabled state [ 2208.648131] audit: type=1400 audit(1427382801.706:238): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=6901 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 2208.648223] audit: type=1400 audit(1427382801.706:239): apparmor=DENIED operation=open profile=/usr/lib/libvirt/virt-aa-helper name=/dev/shm/lttng-ust-wait-5 pid=6901 comm=virt-aa-helper requested_mask=r denied_mask=r fsuid=0 ouid=0 [ 2209.018989] audit: type=1400 audit(1427382802.074:240): apparmor=STATUS operation=profile_remove profile=unconfined name=libvirt-9d578815-a1e9-4596-aef9-a70717574f0e pid=6904 comm=apparmor_parser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434999 Title: Creating a new VM in virt-manager fails because of apparmor permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1434999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043541] Re: radeon 0000:00:01.0: couldn't schedule ib
On saucy, with kernel 3.11.0-2-generic, I sometimes get the same error message when having Radeon DPM enabled (radeon.dpm=1). Unity desktop then freezes and after a few seconds, the screen turns black. However, I can switch to the console and reboot. When leaving DPM disabled (radeon,dpm=0), I don't run into this problem. In any case, my computer always boots fine. This is some hopefully relevant output that I got by 'grep radeon /var/log/kern.log' (DPM enabled): Aug 15 11:08:04 beifang kernel: [4.171526] [drm] radeon kernel modesetting enabled. Aug 15 11:08:04 beifang kernel: [4.282475] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 11:08:04 beifang kernel: [4.291115] radeon :00:01.0: VRAM: 1024M 0x - 0x3FFF (1024M used) Aug 15 11:08:04 beifang kernel: [4.291120] radeon :00:01.0: GTT: 512M 0x4000 - 0x5FFF Aug 15 11:08:04 beifang kernel: [4.298334] [drm] radeon: 1024M of VRAM memory ready Aug 15 11:08:04 beifang kernel: [4.298336] [drm] radeon: 512M of GTT memory ready. Aug 15 11:08:04 beifang kernel: [4.346703] radeon :00:01.0: WB enabled Aug 15 11:08:04 beifang kernel: [4.346710] radeon :00:01.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x88041ea8fc00 Aug 15 11:08:04 beifang kernel: [4.347447] radeon :00:01.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc900125b5a18 Aug 15 11:08:04 beifang kernel: [4.347449] radeon :00:01.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x88041ea8fc04 Aug 15 11:08:04 beifang kernel: [4.347452] radeon :00:01.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x88041ea8fc08 Aug 15 11:08:04 beifang kernel: [4.347454] radeon :00:01.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x88041ea8fc0c Aug 15 11:08:04 beifang kernel: [4.347456] radeon :00:01.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x88041ea8fc10 Aug 15 11:08:04 beifang kernel: [4.348164] radeon :00:01.0: irq 57 for MSI/MSI-X Aug 15 11:08:04 beifang kernel: [4.348332] radeon :00:01.0: radeon: using MSI. Aug 15 11:08:04 beifang kernel: [4.349755] [drm] radeon: irq initialized. Aug 15 11:08:04 beifang kernel: [4.567511] [drm] radeon: power management initialized Aug 15 11:08:05 beifang kernel: [4.751046] fbcon: radeondrmfb (fb0) is primary device Aug 15 11:08:05 beifang kernel: [4.850214] radeon :00:01.0: fb0: radeondrmfb frame buffer device Aug 15 11:08:05 beifang kernel: [4.850215] radeon :00:01.0: registered panic notifier Aug 15 11:08:05 beifang kernel: [4.851477] [drm] Initialized radeon 2.34.0 20080528 for :00:01.0 on minor 0 Aug 15 11:14:42 beifang kernel: [5.519888] [drm] radeon kernel modesetting enabled. Aug 15 11:14:42 beifang kernel: [5.519925] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Aug 15 11:14:42 beifang kernel: [5.520701] radeon :00:01.0: VRAM: 1024M 0x - 0x3FFF (1024M used) Aug 15 11:14:42 beifang kernel: [5.520704] radeon :00:01.0: GTT: 512M 0x4000 - 0x5FFF Aug 15 11:14:42 beifang kernel: [5.521658] [drm] radeon: 1024M of VRAM memory ready Aug 15 11:14:42 beifang kernel: [5.521659] [drm] radeon: 512M of GTT memory ready. Aug 15 11:14:42 beifang kernel: [5.549871] radeon :00:01.0: WB enabled Aug 15 11:14:42 beifang kernel: [5.549876] radeon :00:01.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x8803f8a2ec00 Aug 15 11:14:42 beifang kernel: [5.550625] radeon :00:01.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012cb5a18 Aug 15 11:14:42 beifang kernel: [5.550628] radeon :00:01.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x8803f8a2ec04 Aug 15 11:14:42 beifang kernel: [5.550630] radeon :00:01.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x8803f8a2ec08 Aug 15 11:14:42 beifang kernel: [5.550633] radeon :00:01.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x8803f8a2ec0c Aug 15 11:14:42 beifang kernel: [5.550635] radeon :00:01.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x8803f8a2ec10 Aug 15 11:14:42 beifang kernel: [5.550852] radeon :00:01.0: irq 56 for MSI/MSI-X Aug 15 11:14:42 beifang kernel: [5.550865] radeon :00:01.0: radeon: using MSI. Aug 15 11:14:42 beifang kernel: [5.551522] [drm] radeon: irq initialized. Aug 15 11:14:42 beifang kernel: [5.818960] [drm] radeon: dpm initialized Aug 15 11:14:42 beifang kernel: [6.037287] fbcon: radeondrmfb (fb0) is primary device Aug 15 11:14:42 beifang
[Bug 1167567] Re: efibootmgr can not create new entry due to ENOSPC error
*** This bug is a duplicate of bug 1167622 *** https://bugs.launchpad.net/bugs/1167622 ** This bug has been marked a duplicate of bug 1167622 Cannot change EFI variables using efibootmgr (raring regression) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167567 Title: efibootmgr can not create new entry due to ENOSPC error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1146868] Re: cannot mount /sys/firmware/efi/efivars on boot
In the meantime, I have erased the contents of my EFI parition and reinstalled grub to it. Now, my computer boots fine again, also with 3.8.0-12-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1146868 Title: cannot mount /sys/firmware/efi/efivars on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1146868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1146868] Re: cannot mount /sys/firmware/efi/efivars on boot
With 3.8.0-12-generic, my computer with an ASRock FM2A75 Pro4-M mainboard, which booted fine with 3.8.0-11-generic in UEFI mode, hangs on boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1146868 Title: cannot mount /sys/firmware/efi/efivars on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1146868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Since having updated to the latest linux image (linux- image-3.8.0-6-generic_3.8.0-6.11_amd64.deb), which was rebased to kernel version 3.8-rc7, a few days ago, I have not experienced any freezes of unity. Even when using firefox and doing excessive scrolling, which was very likely to cause freezes of my computer, before. So, it looks like the latest upstream kernel solved the problem in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102660] Re: Ubuntu Raring Hard Freezes with AMD Driver
Same problem here on an AMD A4-5300 APU using the radeon driver. Freezing particularly occurs when I scroll in firefox. Interestingly, when using the chromium-browser instead, this problem occurs much less frequently. As soon as the freeze occurs, unity does not respond to mouse and keyboard input any longer. However, I can use magic SysRq keys Alt + Print + REISUB to reboot my computer. So, the kernel (3.0.8-5) is still alive. It would be great, if someone could figure where this annoying problem is located. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102660 Title: Ubuntu Raring Hard Freezes with AMD Driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
