[Bug 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

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 Bugs, which is subscribed to Ubuntu.

[Bug 1552355] Re: Unprivileged lxc will not start after being stopped

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

[Bug 1552355] Re: Unprivileged lxc will not start after being stopped

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

[Bug 1552372] [NEW] [FFE] support cgroup namespace unshare

Public bug reported: unshare should support a [-c,--cgroup=] option to exploit the new cgroup namespaces which the xenial kernel now supports. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of

Re: [Bug 1552355] [NEW] Unprivileged lxc will not start after being stopped

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

Re: [Bug 1552355] [NEW] Unprivileged lxc will not start after being stopped

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 Bugs, which is

Re: [Bug 1552355] [NEW] Unprivileged lxc will not start after being stopped

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

Re: [Bug 1552355] [NEW] Unprivileged lxc will not start after being stopped

Actually in my case it actually segfaults -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552355 Title: Unprivileged lxc will not start after being stopped To manage notifications about this bug go

[Bug 1551923] [NEW] mount name=systemd

/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

[Bug 1551923] [NEW] mount name=systemd

/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

[Bug 1551854] Re: LXD bootstrap issues on xenial

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 Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1517539] Re: Libvirt KVM can not create snapshot (with qemu-guest-agent)

Hi Alan - does that mean the 'verification-done' tag should be changed to verification-failed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517539 Title: Libvirt KVM can not create snapshot (with

[Bug 1551854] Re: LXD bootstrap issues on xenial

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 /

[Bug 1551854] Re: LXD bootstrap issues on xenial

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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551854 Title: LXD bootstrap issues on xenial To manage

[Bug 1386465] Re: apparmor profile prevents libvirtd from creating a socket

Thomas, would you mind filing a new bug using apport? In particular I'd like to see any local changes to your /etc/libvirt/libvirtd.conf and /etc/default/libvirt-bin and see the upgrade log if possible. If you can reproduce at will in clean vms by taking particular steps, that would be great.

[Bug 1519079] Re: Xenial container on Xenial host no longer runs systemd and can't get an IP address

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519079 Title: Xenial container on Xenial host no longer runs systemd and can't

[Bug 1519079] Re: Xenial container on Xenial host no longer runs systemd and can't get an IP address

** No longer affects: lxcfs (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519079 Title: Xenial container on Xenial host no longer runs systemd and can't get an IP address To

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

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:

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android

[Bug 1546445] Re: support vhost user without specifying vhostforce

** 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

[Bug 1546445] Re: support vhost user without specifying vhostforce

** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support

[Bug 1546674] Re: virt-aa-helper Apparmor profile missing rules for name resolution

** Changed in: libvirt (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546674 Title: virt-aa-helper Apparmor profile missing rules for name resolution

[Bug 1524737] Re: systemd presents hugetblfs at /dev/hugepages

** 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

[Bug 1524737] Re: systemd presents hugetblfs at /dev/hugepages

** No longer affects: libvirt (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524737 Title: systemd presents hugetblfs at /dev/hugepages To manage notifications about this bug go to:

[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

Adding 'capability mknod' to /etc/apparmor.d/abstractions/libvirt-qemu solves it for me. I'm not sure we want to add that to all VMs. Do we need to add it to the policy during virt-aa-helper? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

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

[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393842 Title: libvirt does not grant

[Bug 1549665] Re: getch returning ENOENT

** Package changed: ncurses (Ubuntu) => sc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549665 Title: getch returning ENOENT To manage notifications about this bug go to:

Re: [Bug 1549665] Re: getch returning ENOENT

D'oh. Thanks, I'll patch sc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549665 Title: getch returning ENOENT To manage notifications about this bug go to:

[Bug 1549665] Re: getch returning ENOENT

Hm, maybe this is a bug in the sc program after all. It seems to be calling notimeout(stdscr, TRUE). i don't know why it's doing that, or why it never seemed to do anything in older releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1549665] [NEW] getch returning ENOENT

Public bug reported: The program 'sc' was recently recompiled (according to changelog) for ncurses6. Since that happened, its call to getch() (in lex.c:nmgetch() around line 680) returns -1 with errno ENOENT. The version in older releases properly waits for an input character. ** Affects:

[Bug 1342083] Re: "Failed to create chardev" due to apparmor DENIED execute of "/usr/lib/pt_chown"

Oh, I misread, it's only a sub-policy that has cap-fowner. pt_chown is not exactly trusted to begin with, so I'm not sure i want to allow all vms to run it with cap-fowner. Not sure what the best way forward is. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1342083] Re: "Failed to create chardev" due to apparmor DENIED execute of "/usr/lib/pt_chown"

Thanks - that's very odd, since your file actually does include 'capability fowner', which is what the syslog says was denied. Are these qemu vms, or are they containers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1342083] Re: "Failed to create chardev" due to apparmor DENIED execute of "/usr/lib/pt_chown"

Hi, you should be able to work around it by adding capability fowner, to that file. Note that /etc/apparmor.d/abstractions/libvirt-qemu on my system already has that. I wonder whether your file libvirt-qemu abstractions file may be out of date? Can you paste it here? -- You received this

Re: [Bug 1547208] Re: package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new virtlockd initd script

Quoting Mikhail S Medvedev (mmedv...@us.ibm.com): > So without the daemon, I would expect you should not be able to do > '/etc/init.d/virtlockd start'. Why apt-get install is not failing for systemctl start virtlockd works fine now interestingly, 0 ✓ serge@sl ~ $ sudo systemctl stop virtlockd

Re: [Bug 1547208] Re: package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new virtlockd initd script

daemon is not installed here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547208 Title: package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new virtlockd initd script To manage

[Bug 1535494] Re: Fix numa_node_to_cpus patch

Test on a amd64 qemu vm with 82 cpus (though no numa config). Wily and trusty both seemed good. ** 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 numactl in Ubuntu.

[Bug 1535494] Re: Fix numa_node_to_cpus patch

Test on a amd64 qemu vm with 82 cpus (though no numa config). Wily and trusty both seemed good. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1547208] Re: package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new virtlockd initd script

Install (... really, upgrade) did not fail for me, but virtlogd frequently fails to start on boot for me, leading to mysterious failures starting VMs. Starting it by hand fixes it. ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance:

Re: [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Quoting Bas Zoetekouw (b...@debian.org): > I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is > still linux-image-4.5.0-040500rc4-generic and lxc is > 1.1.5-0ubuntu0.15.10.3 from wily-updates. > > Unfortunately, when I now start the lxc container, I seem to hit a > different

Re: [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Quoting Bas Zoetekouw (b...@debian.org): > I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is > still linux-image-4.5.0-040500rc4-generic and lxc is > 1.1.5-0ubuntu0.15.10.3 from wily-updates. > > Unfortunately, when I now start the lxc container, I seem to hit a > different

Re: [Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

Yes, you can find them from the publishing history page at https://launchpad.net/ubuntu/+source/qemu/+publishinghistory : https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/8368971 and https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-2ubuntu1.20/+build/8116598 -- You

Re: [Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

Yes, you can find them from the publishing history page at https://launchpad.net/ubuntu/+source/qemu/+publishinghistory : https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/8368971 and https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-2ubuntu1.20/+build/8116598 -- You

Re: [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

Interesting. It is still this way in libvirt git HEAD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on

Re: [Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

Looking at the source, virt-aa-helper should still be doing the right thing to add an exception for that channel. For a VM which has that channel, could you post the /etc/apparmor.d/libvirt/libvirt-.files replacing with the vm's uuid, of course. -- You received this bug notification because

Re: [Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

Thanks - two most likely explanations are that there was a regression in the apparmor policy, or the filename has changed Could you check syslog for a related DENIED message in syslog and post it here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

** 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. https://bugs.launchpad.net/bugs/1545821 Title: Regression: spice usbredirect causes windows client to

[Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

** Changed in: qemu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545821 Title: Regression: spice usbredirect causes windows client to crash To manage

[Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

Thanks for submitting this bug report. Based on the changelog entries, I would guess that this was introduced by the fix to CVE-2015-8619. Could you verify that downgrading to 2.0.0+dfsg-2ubuntu1.21 also fixes it for you? ** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu) ** CVE added:

[Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash

Thanks for submitting this bug report. Based on the changelog entries, I would guess that this was introduced by the fix to CVE-2015-8619. Could you verify that downgrading to 2.0.0+dfsg-2ubuntu1.21 also fixes it for you? ** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu) ** CVE added:

[Bug 1545969] me too

Just commenting that this bug is affecting me too on fully uptodate xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545969 Title: webbrowser-app crashed with SIGABRT To manage notifications

Re: [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Thanks - do make sure to log back in after the update. The xenial systemd would fail because there you must have libpam-cgfs to get your own cgroups for lxc. In wily iirc that should not be required. -- You received this bug notification because you are a member of Ubuntu Server Team, which is

Re: [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Thanks - do make sure to log back in after the update. The xenial systemd would fail because there you must have libpam-cgfs to get your own cgroups for lxc. In wily iirc that should not be required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1535494] Re: Fix numa_node_to_cpus patch

** Description changed: + = + SRU Justification + same justification as for bug 1358835. It would + be great to have the same test cases run as in that + bug. + = + In bug 1358835 we applied a fix to

[Bug 1535494] Re: Fix numa_node_to_cpus patch

** Description changed: + = + SRU Justification + same justification as for bug 1358835. It would + be great to have the same test cases run as in that + bug. + = + In bug 1358835 we applied a fix to

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

@pitti, to reproduce in a fresh vm, 1. apt-get install qemu-kvm libvirt-bin 2. follow instructions at https://wiki.ubuntu.com/SergeHallyn_libvirtnest , in particular: a. wget http://people.canonical.com/~serge/cdboot.xml b. wget -O mini.iso

[Bug 1539349] Re: sleep from invalid context in aa_move_mount

Wait, that's not a valid test is it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539349 Title: sleep from invalid context in aa_move_mount To manage notifications about this bug go to:

[Bug 1539349] Re: sleep from invalid context in aa_move_mount

I get no warnings with 4.2.0-29-generic #34-Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539349 Title: sleep from invalid context in aa_move_mount To manage notifications about this bug

[Bug 1539349] Re: sleep from invalid context in aa_move_mount

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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539349 Title: sleep from invalid context

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Oh, right, something with the pids controller enabled. Still want to make sure he's using the right systemd version, since his appears not to be fixed otherwise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Oh, right, something with the pids controller enabled. Still want to make sure he's using the right systemd version, since his appears not to be fixed otherwise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Just to be sure, can you show the systemd version you were using here? The intent was to check with systemd from wily-proposed, with the regular wily kernel. In particular, an upstream kernel would be expected to fail by default without setting an extra apparmor flag in the container

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

Just to be sure, can you show the systemd version you were using here? The intent was to check with systemd from wily-proposed, with the regular wily kernel. In particular, an upstream kernel would be expected to fail by default without setting an extra apparmor flag in the container

[Bug 1545884] Re: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

Fascinating, src/useradd.c still has is_sub_uid = sub_uid_file_present () && !rflg && (!user_id || (user_id <= uid_max && user_id >= uid_min)); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1545884] Re: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

Oh, the bug is that process_flags() is being called after we check for rflg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545884 Title: Xenial's shadow regresses subid allocation logic (wastes

[Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Changed in: strongswan (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1535951 Title: Please merge strongswan 5.3.5-1 (main)

[Bug 1545884] Re: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

I see. The fix for that is not in the upstream PR, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545884 Title: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

[Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Changed in: strongswan (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535951 Title: Please merge strongswan 5.3.5-1 (main) from Debian unstable

[Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Changed in: strongswan (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1535951 Title: Please merge strongswan 5.3.5-1 (main) from

[Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Changed in: strongswan (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535951 Title: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

[Bug 1545884] Re: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

Also, on my xenial laptop i just added a new user, and got: xxx:731073:65536 So I'm curious what happened on your host? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545884 Title: Xenial's

[Bug 1545884] Re: Xenial's shadow regresses subid allocation logic (wastes uids and gids)

Hm, near as I can tell debian/patches/1000_configure_userns is still applied in xenial's shadow and has that content. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545884 Title: Xenial's shadow

[Bug 1541902] Re: Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM

** Changed in: qemu (Ubuntu) Status: New => Incomplete -- 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/1541902 Title: Enable DDW on qemu aiming GPU passthrough performance on

[Bug 1541902] Re: Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM

** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541902 Title: Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM To

Re: [Bug 1546674] [NEW] virt-aa-helper Apparmor profile missing rules for name resolution

Thanks I see that here too. status confirmed ** Changed in: libvirt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546674 Title: virt-aa-helper Apparmor

[Bug 1545687] Re: Unable to launch a guest using libvirt on PowerNV Ubuntu Host

Hi, Your qemu is not the latest version. The current xenial version is 1:2.5+dfsg-5ubuntu1 . Does upgrading help at all? What does 'kvm-ok' show? What does 'ls -l /dev/kvm' show? Can you do kvm -vnc :1 -monitor stdio QEMU 2.5.0 monitor - type 'help' for more information (qemu) info kvm kvm

[Bug 1546775] [NEW] Please pull cgroup namespaces

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,

[Bug 1529079] Re: Can't start virtual machines after upgrade to Xenial

Lowering priority since there is a workaround. Stilll not clear whether this is a bug in systemd-machined or in libvirt's use of it. ** Changed in: libvirt (Ubuntu) Importance: High => Medium ** Changed in: systemd (Ubuntu) Importance: High => Medium -- You received this bug

[Bug 1529079] Re: Can't start virtual machines after upgrade to Xenial

The problem is introduced by systemd-machined, which is being provided by the systemd-container package. The workaround is to apt-get purge systemd-container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1529079] Re: Can't start virtual machines after upgrade to Xenial

Feb 17 13:13:19 sl libvirtd[9909]: DBUS_METHOD_CALL: 'org.freedesktop.machine1.Manager.CreateMachineWithNetwork' on '/org/freedesktop/machine1' at 'org.freedesktop.machine1' Feb 17 13:13:19 sl libvirtd[9909]: DBUS_METHOD_ERROR: 'org.freedesktop.machine1.Manager.CreateMachineWithNetwork' on

[Bug 1529079] Re: Can't start virtual machines after upgrade to Xenial

So I can reproduce this now that I've updated to xenial; smb and arges who did fresh installs cannot. Interesting. ** Changed in: libvirt (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

Re: [Bug 1544157] Re: lxc exec not working in xenial

Oh, yeah, systemd will start it when lxd starts. Please start lxd first (by doing a 'lxc list'), then stop cgmanager and try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544157 Title: lxc

Re: [Bug 1544157] Re: lxc exec not working in xenial

Oh, yeah, systemd will start it when lxd starts. Please start lxd first (by doing a 'lxc list'), then stop cgmanager and try again. -- 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/1544157

[Bug 1544157] Re: lxc exec not working in xenial

Apparently the fixes we need should already be in the xenial lxc packages. Could you please try (in one root terminal) systemctl stop cgmanager then see whether you're still able to start apps? (If not, then in that terminal again do 'systemctl start cgmanager') -- You received this bug

[Bug 1544157] Re: lxc exec not working in xenial

Apparently the fixes we need should already be in the xenial lxc packages. Could you please try (in one root terminal) systemctl stop cgmanager then see whether you're still able to start apps? (If not, then in that terminal again do 'systemctl start cgmanager') -- You received this bug

[Bug 1544157] Re: lxc exec not working in xenial

** Changed in: lxd (Ubuntu) Status: Incomplete => Fix Committed ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Fix Committed ** Changed in: lxd (Ubuntu) Importance: Undecided => High ** Changed in: lxc

[Bug 1544157] Re: lxc exec not working in xenial

** Changed in: lxd (Ubuntu) Status: Incomplete => Fix Committed ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Fix Committed ** Changed in: lxd (Ubuntu) Importance: Undecided => High ** Changed in: lxc

Re: [Bug 1544157] Re: lxc exec not working in xenial

Thanks. fwiw we need at least up to commit 3939a22a481 from git to fix this. I'll mark it fix committed as the fix is in git and ppa, and will hit xenial with the next merge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1539548] Re: Ubuntu 16.04: not possible to install qemu-system-common

Thanks, setting the bug status to Invalid meaning "cannot reproduce". ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Changed in: sysvinit (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 1539548] Re: Ubuntu 16.04: not possible to install qemu-system-common

Thanks, setting the bug status to Invalid meaning "cannot reproduce". ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Changed in: sysvinit (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1545839] [NEW] Does not cause watershed to be installed

Public bug reported: lvm2 Depends: on watershed, but several cases (including my laptop) appear to have lvm2 without watershed installed. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1545839] Re: Does not cause watershed to be installed

No, wait, invalid on my laptop at least. ** Changed in: lvm2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545839 Title: Does not cause watershed to be

[Bug 1545839] Re: Does not cause watershed to be installed

apt-cache show lvm2 Package: lvm2 Priority: optional Section: admin Installed-Size: 2101 Maintainer: Ubuntu Developers Original-Maintainer: Debian LVM Team Architecture: amd64 Version: 2.02.133-1ubuntu5

[Bug 1539548] Re: Ubuntu 16.04: not possible to install qemu-system-common

Thanks for reporting this bug. mountkernfs should not be a problem, here is its description: # Short-Description: Mount kernel virtual file systems. # Description: Mount initial set of virtual filesystems the kernel #provides and that are required by everything. I'll

[Bug 1539548] Re: Ubuntu 16.04: not possible to install qemu-system-common

Thanks for reporting this bug. mountkernfs should not be a problem, here is its description: # Short-Description: Mount kernel virtual file systems. # Description: Mount initial set of virtual filesystems the kernel #provides and that are required by everything. I'll

[Bug 1481295] Re: virt-manager after upgrade: Error polling connection 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null)

Succeeded here on wily. ** Tags removed: verification-needed vivid ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1481295 Title: virt-manager after

[Bug 1481295] Re: virt-manager after upgrade: Error polling connection 'qemu:///system': internal error: could not get interface XML description: File operation failed - Failed to read (null)

Succeeded here on wily. ** Tags removed: verification-needed vivid ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481295 Title: virt-manager after upgrade: Error

[Blueprint servercloud-x-server-core] General server work for Xenial

Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-15.11: [serge-hallyn] etckeeper: DONE [paelzer] NIS merge: DONE Work items for ubuntu-15.12: [raharper] : tgt merge (bug 1524982): DONE [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE

[Bug 1541736] Re: Sync bacula 7.0.5+dfsg-4 (main) from Debian unstable (main)

As discussed in #ubuntu-devel, I synced the package, and it will presumably sit in proposed until archive admins demote. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1541736

[Bug 1541736] Re: Sync bacula 7.0.5+dfsg-4 (main) from Debian unstable (main)

As discussed in #ubuntu-devel, I synced the package, and it will presumably sit in proposed until archive admins demote. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541736 Title: Sync

<    2   3   4   5   6   7   8   9   10   11   >