[Bug 1368815] Re: qemu-img convert intermittently corrupts output images
Thanks for the information. Looks like we can apply these in debian too. ** Also affects: qemu (Ubuntu Utopic) Importance: High Status: Triaged ** Also affects: qemu (Ubuntu Vivid) 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/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1368815/+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 1381383] Re: Vm destroyed when created with virsh create without --autodestroy
I'm marking this low priority per guidelines since there is a workaround (use virsh define). However it most certainly looks like a bug, especially since --autodestroy is listed as an option in the help usage. ** Summary changed: - Vm destroyed when created virsh create without --autodestroy + Vm destroyed when created with virsh create without --autodestroy ** Changed in: libvirt (Ubuntu) Importance: Undecided = Low ** Changed in: libvirt (Ubuntu) Status: Invalid = 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/1381383 Title: Vm destroyed when created with virsh create without --autodestroy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+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
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
The minimal PATH comes from getconf -a | grep ^PATH (if confstr were not available then lxc would actually default to a longer PATH) status: invalid ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+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
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
I'm saying this is not a bug because the limited path is by design. Your system in fact is telling lxc which path to use as the default. If you think that rather than take the value from the system through sysconf, we should always use a longer PATH, then that could be discussed on the lxc-devel mailing list. Really to me the bug seems to be that sysconf(_SC_PATH) on ubuntu isn't giving the path that root gets by default. -- 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+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 1384327] Re: lxc-attach --clear-env results in a limited $PATH in the container
Looks like the value actually comes straight from a #define in the glibc source code. As such, I think it would be pretty reasonable to change lxc to always use its own path. ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: Invalid = 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+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
Re: [Bug 1379340] [NEW] qemu-kvm guest panic for smp trusty guests
affects: ubuntu/qemu importance: high affects: qemu importance: high ** Also affects: qemu (Ubuntu) Importance: High Status: New ** Also affects: qemu Importance: High Status: New ** No longer affects: qemu-kvm (Ubuntu) -- 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/1379340 Title: qemu-kvm guest panic for smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1379340/+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 1380516] [NEW] lxc-container-default-with-nesting profile should allow bind mounts under home
Public bug reported: Currently if you run a container with lxc-container-default-with- nesting profile, you can run privileged containers inside that, but not unprivileged containers. The special cases we add for /var/lib/lxc should also be added for $HOME/.local/share/lxc. ** Affects: lxc (Ubuntu) Importance: Medium Status: 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/1380516 Title: lxc-container-default-with-nesting profile should allow bind mounts under home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1380516/+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 1380519] [NEW] lxc-user-nic should run in its own apparmor profile
Public bug reported: The lxc-user-nic program is a setuid-root program to create veth nics and hook them to the host bridge and unprivileged containers. It should run under a very tight apparmor profile. (Make sure to test with ovs bridges as well, as its call-out to ovs- vsctl may have unexpected requirements) ** Affects: lxc (Ubuntu) Importance: High Status: 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/1380519 Title: lxc-user-nic should run in its own apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1380519/+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 1379030] Re: Extra lxc.mount.auto entry being added to config file
A proposed fix has been sent to the mailing list, and will probably be applied in utopic today. In the meantime you can work around this by using the 'append_config_item' method instead of set_config_item. (Note that the C API does not have this same behavior, so this is only for the python bindings) -- 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/1379030 Title: Extra lxc.mount.auto entry being added to config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379030/+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 1376717] Re: lxc fails to install under systemd
** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1376717 Title: lxc fails to install under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1376717/+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 1357103] Re: apparmor denied a golang build inside a container
** Changed in: lxc (Ubuntu) Status: New = 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/1357103 Title: apparmor denied a golang build inside a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1357103/+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 1358306] Re: lxc postinst incorrectly chooses network address to use
Thanks. This'll need to be fixed in the lxc.preinst. ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1358306 Title: lxc postinst incorrectly chooses network address to use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1358306/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1379441] Re: installation fails when /var/cache/lxc is read-only
Thanks for the bug report and the patch. I'm a bit concerned about supporting this. I understand why you want it, but lxc in general won't work well with a read-only cache, so an install failure early on would seem preferable to a lxc-create failure later on. Would using an overlayfs of the cache in the container have any significant downsides? Or, alternatively, you could simply bind-mount /var/cache/lxc into the container rw, but (if you really don't trust the container) have apparmor deny writes. If we were to go with your fix, I would prefer to do chmod 700 /var/cache/lxc || true because the -w check could fail for reasons other than a ro-fs. ** Changed in: lxc (Ubuntu) Status: New = Incomplete ** Changed in: lxc (Ubuntu) Importance: Undecided = Low -- 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/1379441 Title: installation fails when /var/cache/lxc is read-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+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 1270784] Re: aa-status --enabled failed in LXC container with Permission denied: '/sys/kernel/security/apparmor/profiles'
It actually seems like a bug in aa-status. Note that /sys/kernel/security/apparmor/profiles is not readable by non- root users on the host. Yet non-root users on the host do not see a python traceback when they run 'aa-status --enable'. This also suggests that a container should not provide read access to the file. (Note that the traceback doesn't happen as root in an unprivileged container - there it quietly exits 4 just like for any unprivileged user) -- 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/1270784 Title: aa-status --enabled failed in LXC container with Permission denied: '/sys/kernel/security/apparmor/profiles' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1270784/+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
Re: [Bug 1378738] [NEW] guest os boot stuck with mount operation error
Thanks for reporting this bug. To fix the cgmanager issue, add the line lxc.mount.auto = cgroup:mixed to your container configuration file. That shouldn't explain your hang however. Assuming it doesn't, please run lxc-start -n container -l trace -o debug.out -- /sbin/init debug verbose --debug --verbose And append both the console output and the file debug.out status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1378738 Title: guest os boot stuck with mount operation error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1378738/+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 1324393] Re: Force off fails with Permission denied after upgrading to 14.04
** Changed in: libvirt (Ubuntu) Status: Invalid = Confirmed -- 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/1324393 Title: Force off fails with Permission denied after upgrading to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1324393/+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
Re: [Bug 1379030] [NEW] Extra lxc.mount.auto entry being added to config file
Thanks for submitting this bug 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 subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379030 Title: Extra lxc.mount.auto entry being added to config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379030/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
** Description changed: + = + Impact: qemu VMs cannot be migrated from 12.04-14.04 hosts + Test Case: migrate a vm from p-t host, using disk on a NFS share. On the 14.04 host, use + kvm -M pc-1.0-precise [...] -incoming tcp:0.0.0.0: + and on the 12.04 host use + kvm -M pc-1.0 [...] -monitor stdio + then on the monitor type + migrate tcp:0.0.0.0: + + Regression Potential: This introduces a new machine type. In precise it will make the new machine type the default, but it is identical to the old default. In Trusty it is not the default. + = + Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04. https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution. As a part of this, we need to define the pc-1.0-precise machine type which can accept incoming migrations from pc-1.0 machines from a precise host. Since this machine type requires the old precise pxe-virtio rom, this bug is blocked on the FFE for the new ipxe-precise package, bug 1374617. ** Description changed: = Impact: qemu VMs cannot be migrated from 12.04-14.04 hosts - Test Case: migrate a vm from p-t host, using disk on a NFS share. On the 14.04 host, use - kvm -M pc-1.0-precise [...] -incoming tcp:0.0.0.0: + Test Case: XXX NOTE XXX This requires the fix for bug 1374617 as well. + migrate a vm from p-t host, using disk on a NFS share. On the 14.04 host, use + kvm -M pc-1.0-precise [...] -incoming tcp:0.0.0.0: and on the 12.04 host use - kvm -M pc-1.0 [...] -monitor stdio + kvm -M pc-1.0 [...] -monitor stdio then on the monitor type - migrate tcp:0.0.0.0: + migrate tcp:0.0.0.0: Regression Potential: This introduces a new machine type. In precise it will make the new machine type the default, but it is identical to the old default. In Trusty it is not the default. = Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04. https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution. As a part of this, we need to define the pc-1.0-precise machine type which can accept incoming migrations from pc-1.0 machines from a precise host. Since this machine type requires the old precise pxe-virtio rom, this bug is blocked on the FFE for the new ipxe-precise package, bug 1374617. -- 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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
Re: [Bug 1377973] [NEW] lxc-destroy/lxc-stop gets stuck
Quoting Nikola Krzalic (nik...@krzalic.com): Looks like the lxc-start command got stuck, after killing the process everything went back to normal. ... still, I find it a bit strange that not even lxc-ls was working properly Right, we should find a way to keep lxc-stop and lxc-ls from hanging in this case. Perhaps after a (reasonably long) timeout we should assume it is dead, hard-kill the container (in this case the owner of the command socket), and continue. (marking medium importance rather than high, per guidelines, since it can be detected and worked around) status: confirmed importance: medium ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: Incomplete = Confirmed -- 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/1377973 Title: lxc-destroy/lxc-stop gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
Using the ipxe-precise package from ppa:serge-hallyn/qemu-migration2, migration from 12.04-14.04 (using -proposed for both) succeeded. I also ran a full test-qemu.py from lp:qa-regressoin-testing with no errors. ** 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 qemu in Ubuntu. https://bugs.launchpad.net/bugs/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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
Re: [Bug 1377973] [NEW] lxc-destroy/lxc-stop gets stuck
thanks for reporting this bug. Could you please show: 1. The result of 'netstat -x | grep lxc' 2. ps -ef | grep lxc status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1377973 Title: lxc-destroy/lxc-stop gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
We've discussed this in #ubuntu-release and decided to not support the pc-1.0-precise machine type after 14.04. Therefore the utopic (FFE) bug is wontfix, and we will only seek SRU for 14.04. ** Changed in: qemu (Ubuntu) Status: Confirmed = 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1373981] Re: ubuntu 14.10 server, amd64 - lxc-start fails to start container
** Package changed: lxc (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Description changed: + = + ec2-run-instances ami-3021fb58 -t m1.small + + ssh into the instance, + + sudo ip link add type veth + + fails. I also often cannot log in. I think it's just a bad + ami, but am not sure. + = I had previously created an lxc container successfully using either: $ sudo lxc-create -t download -n test_cn -or- $ sudo lxc-create -t ubuntu -n test_cn However... when trying to start it fails with the following? - + $ sudo lxc-start -n test_cn lxc-start: failed to create vethBQ6TPB-vethV9VF9A : Operation not supported lxc-start: failed to create netdev lxc-start: failed to create the network lxc-start: failed to spawn 'test_cn' lxc-start: The container failed to start. lxc-start: Additional information can be obtained by setting the --logfile and --log-priority options. To check if the veth kernel module is loaded I updated the server and rebooted I ran sudo modprobe veth and it shows an error also? $ sudo modprobe veth modprobe: ERROR: could not insert 'veth': Cannot allocate memory - This server is running on AWS EC2. $ uname -a Linux ip-10-69-148-9 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- 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/1373981 Title: ubuntu 14.10 server, amd64 - lxc-start fails to start container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373981/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
Build log is at: https://launchpad.net/~serge-hallyn/+archive/ubuntu /qemu-migration2/+build/6413926/+files/buildlog_ubuntu-utopic- amd64.qemu_2.1%2Bdfsg-4ubuntu5%7Emigration3_UPLOADING.txt.gz -- 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
upgrade log: ubuntu@migrate-u:~$ sudo apt-get install qemu-system-x86 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: samba vde2 sgabios ovmf The following packages will be upgraded: qemu-system-x86 1 upgraded, 0 newly installed, 0 to remove and 62 not upgraded. Need to get 2,033 kB of archives. After this operation, 22.5 kB of additional disk space will be used. Get:1 http://ppa.launchpad.net/serge-hallyn/qemu-migration2/ubuntu/ utopic/main qemu-system-x86 amd64 2.1+dfsg-4ubuntu5~migration3 [2,033 kB] Fetched 2,033 kB in 0s (47.3 MB/s) (Reading database ... 51987 files and directories currently installed.) Preparing to unpack .../qemu-system-x86_2.1+dfsg-4ubuntu5~migration3_amd64.deb ... Unpacking qemu-system-x86 (2.1+dfsg-4ubuntu5~migration3) over (2.1+dfsg-4ubuntu4) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... -- 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1375910] Re: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Also affects: libvirt (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Precise) Importance: Undecided = High ** Changed in: libvirt (Ubuntu Trusty) Importance: Undecided = High ** Description changed: + == + Impact: libvirt package upgrade can fail if user deletes /etc/libvirt/qemu.conf + Test case: + sudo apt-get install libvirt-bin + sudo rm /etc/libvirt/qemu.conf + sudo apt-get install --reinstall libvirt-bin + Regresion potential: none, we only check that the file is present before trying to chown+chmod it. + == + I ran sudo apt-get update sudo apt-get upgrade After that, the differents programs installed ans updated but libvirt-bin can't be configure by dpkg cause /etc/libvirt/qemu.conf don't exist. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libvirt-bin 1.2.8-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 12:11:16 2014 DuplicateSignature: package:libvirt-bin:1.2.8-0ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-28 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: libvirt Title: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [modified] mtime.conffile..etc.libvirt.qemu.conf: 2014-09-30T12:11:54.303971 -- 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/1375910 Title: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1375910/+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 1375910] Re: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** No longer affects: libvirt (Ubuntu Precise) -- 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/1375910 Title: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1375910/+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 1373981] Re: ubuntu 14.10 server, amd64 - lxc-start fails to start container
Thanks for submitting this bug. To be clear, 'sudo ip link add type veth' also returns an error? Could you tell us which ami and which machine type you used to start the amazon instance? ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1373981 Title: ubuntu 14.10 server, amd64 - lxc-start fails to start container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981/+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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] implement lxc-checkpoint: DONE [tycho-s] design lxc-restart: DONE [tycho-s] criu: hook the network interface up at restart: DONE [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: POSTPONED Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED [hazmat] image based workflow for juju: POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: POSTPONED [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : POSTPONED [tycho-s] re-attach lxc monitor at criu restart: DONE Work items for ubuntu-14.09: [serge-hallyn] design security profiles: POSTPONED [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: POSTPONED [tycho-s] additional criu breakages for basic containers (split up as we find them): POSTPONED [tycho-s] fix dumping ubuntu-cloud containers (missing pid fix): DONE [tycho-s] fix co-mounted cgroup restore bug: INPROGRESS - [tycho-s] fix not being able to checkpoint restored containers: TODO + [tycho-s] fix not being able to checkpoint restored containers: DONE -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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 1374612] [NEW] [FFE] add pc-1.0-precise machine type
Public bug reported: Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04. https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution. As a part of this, we need to define the pc-1.0-precise machine type which can accept incoming migrations from pc-1.0 machines from a precise host. Since this machine type requires the old precise pxe-virtio rom, this bug is blocked on the FFE for the new ipxe-precise package, bug 1374617. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Precise) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Trusty) 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
** Description changed: Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04. https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution. As a part of this, we need to define the pc-1.0-precise machine type which can accept incoming migrations from pc-1.0 machines from a precise host. Since this machine type requires the old precise pxe-virtio rom, this - bug is blocked on the FFE for the new ipxe-precise package. (I will - fill in the bug# here) + bug is blocked on the FFE for the new ipxe-precise package, bug 1374617. -- 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1374622] [NEW] Support migration from 12.04
Public bug reported: Bug 1291321 shows that qemu VMs cannot be migrated from a host running 12.04 to a host running 14.04. https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution. One part of the problem is that libvirt in trusty cannot distinguish a pc-1.0 machine being migrated from 12.04 from a pc-1.0 being migrated from 14.04. libvirt needs a flag to tell it which to use when a pc-1.0 VM is migrated to it. This only needs to be done for Trusty. Any VM running on precise can be migrated to trusty with this flag set, which will change the machine type to pc-1.0-precise. From there on it can be migrated to utopic and beyond with no special casing in libvirt. Note this depends on bugs 1374612 and 1374617, to define the machine type and provide the binary roms which are needed for the pc-1.0-precise machine type to be usable by libvirt. = SRU Justification Impact: VM scannot be migrated from precise to trusty Test case: set up libvirt on a precise and a trusty host; add a root ssh key on the precise host and place it in the authorized_hosts file for root on the tursty host; restart libvirt on the trusty host. start a pc-1.0 vm on precise migrate the vm, i.e.: virsh migrate --live --p2p --tunnelled --copy-storage-all vm1 qemu+ssh://trusty-host-ip/system This should fail. Now edit /etc/libvirt/qemu.conf on the trusty host and add: assume_incoming_qemukvm = 1 restart libvirt. Retry migration, should now work. Regression potential: this should change nothing if the new assume_incoming_qemukvm is not set. = ** Affects: libvirt (Ubuntu) Importance: High Status: Won't Fix ** Affects: libvirt (Ubuntu Trusty) Importance: High Status: New ** Also affects: libvirt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New = Won't Fix ** Changed in: libvirt (Ubuntu Trusty) Importance: Undecided = High ** Changed in: libvirt (Ubuntu) Importance: Undecided = High -- 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/1374622 Title: Support migration from 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1374622/+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 1374612] Re: [FFE] add pc-1.0-precise machine type
** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu Precise) Importance: Undecided = High ** Changed in: qemu (Ubuntu Trusty) 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/1374612 Title: [FFE] add pc-1.0-precise machine type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1374612/+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 1373555] Re: please restrict signal, ptrace and unix mediation to the container
Thanks I'll do some testing. I suspect we'll need to allow access to cgmanager, but otherwise this looks good. ** 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 subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1373555 Title: please restrict signal, ptrace and unix mediation to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373555/+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 1373555] Re: please restrict signal, ptrace and unix mediation to the container
Since you're not restricting dbus, cgmanager is actually unaffected, so this shouldn't restrict nested use at all. ** Changed in: lxc (Ubuntu) Status: Confirmed = 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/1373555 Title: please restrict signal, ptrace and unix mediation to the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373555/+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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS - [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO - [tycho-s] (or serge-hallyn) design lxc-restart: TODO - [tycho-s] criu: hook the network interface up at restart: TODO + [tycho-s] implement lxc-checkpoint: DONE + [tycho-s] design lxc-restart: DONE + [tycho-s] criu: hook the network interface up at restart: DONE [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS - [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO + [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: POSTPONED Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED [hazmat] image based workflow for juju: POSTPONED - [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO + [jjohansen] Provide a test PPA for stacked apparmor profiles: POSTPONED [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : POSTPONED [tycho-s] re-attach lxc monitor at criu restart: DONE Work items for ubuntu-14.09: [serge-hallyn] design security profiles: POSTPONED [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: POSTPONED - [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO + [tycho-s] additional criu breakages for basic containers (split up as we find them): POSTPONED [tycho-s] fix dumping ubuntu-cloud containers (missing pid fix): DONE [tycho-s] fix co-mounted cgroup restore bug: INPROGRESS [tycho-s] fix not being able to checkpoint restored containers: TODO -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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
[Blueprint servercloud-u-server-core] General server work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [serge-hallyn] convert libvirt to cgmanager (4d): DONE [racb] Early cycle merge report: POSTPONED [serge-hallyn] merge qemu: DONE Work items for ubuntu-14.07: [serge-hallyn] cgmanager package into debian: DONE [serge-hallyn] systemd-shim integration for cgmanager: DONE [jamespage] (with raharper) docker 1.0 in 14.04: INPROGRESS Work items for ubuntu-14.08: [racb] Late cycle merge report: TODO [smoser] add simplestreams data to ubuntu core images: TODO [serge-hallyn] triage qemu bugs: DONE [serge-hallyn] go over high prio qemu bugs: DONE [racb] bcache in universe: INPROGRESS [racb] add scribe (https://github.com/facebook/scribe) to universe: POSTPONED [racb] add meteor (https://github.com/meteor/meteor) to universe: POSTPONED Work items for ubuntu-14.09: [smoser] write documentation on the process of how to do image customization in simplestreams: TODO [serge-hallyn] triage libvirt bugs: DONE - [serge-hallyn] go over high prio libvirt bugs: INPROGRESS + [serge-hallyn] go over high prio libvirt bugs: DONE Work items for ubuntu-14.10: [serge-hallyn] discuss cgmanager features through systemd/cgfs (plumbers): POSTPONED determine ssd caching solution (bcache is it): DONE investigate support of ruby for puppet: POSTPONED -- General server work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-server-core -- 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 1038139] Re: Missing running check on init script
Updated init patch which I'll be pushing. --- haproxy.old 2014-09-22 10:52:07.599718882 + +++ haproxy.new 2014-09-22 10:51:34.815653158 + @@ -46,7 +46,9 @@ return 0 fi for pid in $(cat $PIDFILE) ; do - /bin/kill $pid || return 4 +if kill -0 $pid 2/dev/null; then + /bin/kill $pid || return 4 +fi done rm -f $PIDFILE return 0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1038139 Title: Missing running check on init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1038139/+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 1038139] Re: Missing running check on init script
** Description changed: + + SRU Justification: + Impact: 'service haproxy stop' returns 4 if haproxy was already stopped. + Development fix: check whether haproxy is running before trying to kill it + Stable fix: same as development fix + Test Case: + sudo service haproxy start + sudo killall -9 haproxy + sudo service haproxy stop + echo $? + ~= this should print 0, not 4 + sudo service haproxy start + sudo service haproxy stop + ~= make sure this still correctly prints 0. + Regression potential: if done wrongly we could further break the haproxy service stop. + Hi, this is the relevant version information: # lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 dpkg -l haproxy|tail -1 ii haproxy 1.4.18-0ubuntu1 fast and reliable load balancing reverse proxy - When I issue a stop to haproxy via the init script, on line 49 it tries to kill the process and returns 4 in case of failure, which then after iis the exit status of the script itself. + When I issue a stop to haproxy via the init script, on line 49 it tries to kill the process and returns 4 in case of failure, which then after iis the exit status of the script itself. There are many reasons why stopping a process may fail, one of them is that the process wasn't actually running. In that case, I think the exit status of stop should be 0, since the process is stopped. This caused problems in the following scenario: haproxy governed by pacemaker if the haproxy process stops abruptly for some reason (crash, oom-killer), pacemaker will try to stop and start it again, but it will fail to stop (exit 4, expected 0). To work around this, I added a check on the init script to see if the process was running, see patch attached. ** Also affects: haproxy (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1038139 Title: Missing running check on init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1038139/+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 1038139] Re: Missing running check on init script
** Changed in: haproxy (Ubuntu Precise) Importance: Undecided = High ** Changed in: haproxy (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1038139 Title: Missing running check on init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1038139/+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 1365250] Re: nova-compute memory leak
** Also affects: libvirt-python (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libvirt-python (Ubuntu) Importance: Undecided = High ** Changed in: libvirt-python (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt-python in Ubuntu. https://bugs.launchpad.net/bugs/1365250 Title: nova-compute memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1365250/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
@Raphael, if you're having trouble with the virtio network type, then it sounds like either you are not passing the romfile option to qemu in the trusty host (-global virtio-net-pci.romfile=pxe-virtio.rom.12.04), or you do not have the pxe-virtio.rom.12.04 file installed (in /usr/share/qemu/ as a link to /usr/lib/ipxe/qemu/pxe-virtio.rom.12.04. -- 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/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO [tycho-s] (or serge-hallyn) design lxc-restart: TODO [tycho-s] criu: hook the network interface up at restart: TODO [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO Work items for ubuntu-14.08: - [stgraber] Update lxc-start-ephemeral to use the clone function: TODO - [serge-hallyn] (actually hazmat) image based workflow for juju: TODO + [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED + [serge-hallyn] (actually hazmat) image based workflow for juju: POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : TODO [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO Work items for ubuntu-14.09: - [serge-hallyn] design security profiles: TODO - [serge-hallyn] Investigate the syslog namespace and try to get things forward a bit (1d): TODO + [serge-hallyn] design security profiles: POSTPONED + [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: TODO -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO [tycho-s] (or serge-hallyn) design lxc-restart: TODO [tycho-s] criu: hook the network interface up at restart: TODO [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED [serge-hallyn] (actually hazmat) image based workflow for juju: POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : TODO [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO + [tycho-s] re-attach lxc monitor at criu restart: DONE Work items for ubuntu-14.09: [serge-hallyn] design security profiles: POSTPONED [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE - [tycho-s] Design unprivileged checkpoint and restart: TODO + [tycho-s] Design unprivileged checkpoint and restart: POSTPONED -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO [tycho-s] (or serge-hallyn) design lxc-restart: TODO [tycho-s] criu: hook the network interface up at restart: TODO [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED - [serge-hallyn] (actually hazmat) image based workflow for juju: POSTPONED + [hazmat] image based workflow for juju: POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : POSTPONED [tycho-s] re-attach lxc monitor at criu restart: DONE Work items for ubuntu-14.09: [serge-hallyn] design security profiles: POSTPONED [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: POSTPONED [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO [tycho-s] fix dumping ubuntu-cloud containers (missing pid fix): DONE [tycho-s] fix co-mounted cgroup restore bug: INPROGRESS [tycho-s] fix not being able to checkpoint restored containers: TODO -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
On my main server (3.13.0-32-generic with precise userspace) I installed a trusty container with ext3 (LVM) backing store. There I installed uvt and created 4 VMs, 2 precise amd64 and 2 precise i386. I several times did: ubuntu@uvttest:~$ cat list p-precise-server-amd64 p-precise-server-i386 q-precise-server-i386 q-precise-server-amd64 ubuntu@uvttest:~$ for n in `cat list`; do uvt start -fr $n; done ubuntu@uvttest:~$ for n in `cat list`; do tmux splitw -p 25 -t $TMUX_PANE expect vmupgrade.expect $n; done where vmupgrade.expect is: = #!/usr/bin/expect set container [lrange $argv 0 0] spawn ssh $container #expect assword: #send -- ubuntu\r expect $container:~$ send -- export DEBIAN_FRONTEND=noninteractive\r send -- sudo sed -i 's/never/lts/' /etc/update-manager/release-upgrades\r expect assword for ubuntu: send -- ubuntu\r expect $container:~$ send -- sudo apt-get update\r expect $container:~$ send -- sudo do-release-upgrade -f DistUpgradeViewNonInteractive\r set timeout 11000 expect $container:~$ send -- sudo reboot\r = Then I find /lib -name xxx; sudo reboot; find /lib -name xxx; and look through dmesg for errors, then do ubuntu@uvttest:~$ for n in `cat list`; do uvt stop -fr $n; done Alas I've seen no corruption yet. The goal here isn't just to reproduce it, but to do so reliably enough to be able to bisect - this isn't it :( -- 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/1292234 Title: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+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 1367425] Re: [FFE] Upgrade to 1.2.8
** Changed in: libvirt-python (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt-python in Ubuntu. https://bugs.launchpad.net/bugs/1367425 Title: [FFE] Upgrade to 1.2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1367425/+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 1369785] Re: kvm modules not autoloaded on ppc64el
We can become more clever about the packaging later, but this proposed debdiff should 1. clean up the old qemu-system-x86 sysvinit job 2. install a qemu-kvm upstart job on ppcc64le ** Patch added: d1.debdiff https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1369785/+attachment/4206607/+files/d1.debdiff -- 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/1369785 Title: kvm modules not autoloaded on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1369785/+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 1324174] Re: qemu should attempt to re-load kvm_intel to enable nesting at first install
Thanks, the new version fixed the 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 qemu in Ubuntu. https://bugs.launchpad.net/bugs/1324174 Title: qemu should attempt to re-load kvm_intel to enable nesting at first install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1324174/+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 1331081] Re: please split libvirt-driver apparmor abstraction for qemu and containers
** Changed in: libvirt (Ubuntu) Status: In Progress = 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/1331081 Title: please split libvirt-driver apparmor abstraction for qemu and containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1331081/+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 1369785] Re: kvm modules not autoloaded on ppc64el
Seems like the best thing would be to move qemu-system-x86.qemu- kvm.upstart to qemu-system-common.qemu-kvm.upstart (and same with .default and .init) and have the jobs check for the right architectures. ** Changed in: qemu (Ubuntu) Status: New = Triaged ** Changed in: qemu (Ubuntu) Importance: Undecided = Medium -- 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/1369785 Title: kvm modules not autoloaded on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1369785/+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
Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Quoting Raphael Thoma (raphit...@gmx.ch): In the meantime I could find out that the problem only pops up when virtio (or virtio-net) is being used for network devices. With the e1000 nic_type everything is working as expected. Can this be seen as related to this bug? Perhaps, but if so then only as evidence of why we would not want to try to officially support this - there are too many possible remaining incompatibilities to be able to generally say, with confidence, that migration between 12.04 and 14.04 is reliable. -- 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/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1369785] Re: kvm modules not autoloaded on ppc64el
** Changed in: qemu (Ubuntu) Importance: Medium = 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/1369785 Title: kvm modules not autoloaded on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1369785/+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 1368815] Re: qemu-img convert intermittently corrupts output images
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New = Triaged ** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Trusty) Status: New = Triaged ** Changed in: qemu (Ubuntu Trusty) 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/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1368815/+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 1369481] Re: The trusty machine type should stick to the 2.0 version
Thanks for submitting this bug. Indeed we should re-set the trusty machine type to point to 2.0. We could introduce a utopic machine type, but since utopic won't be supported at the next LTS I'm thinking of not doing so. ** 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/1369481 Title: The trusty machine type should stick to the 2.0 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1369481/+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
[Blueprint servercloud-u-server-core] General server work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [serge-hallyn] convert libvirt to cgmanager (4d): DONE [racb] Early cycle merge report: POSTPONED [serge-hallyn] merge qemu: DONE Work items for ubuntu-14.07: [serge-hallyn] cgmanager package into debian: DONE [serge-hallyn] systemd-shim integration for cgmanager: DONE [jamespage] (with raharper) docker 1.0 in 14.04: INPROGRESS Work items for ubuntu-14.08: [racb] Late cycle merge report: TODO [smoser] add simplestreams data to ubuntu core images: TODO [serge-hallyn] triage qemu bugs: DONE [serge-hallyn] go over high prio qemu bugs: DONE [racb] bcache in universe: TODO [racb] add scribe (https://github.com/facebook/scribe) to universe: POSTPONED [racb] add meteor (https://github.com/meteor/meteor) to universe: POSTPONED Work items for ubuntu-14.09: [smoser] write documentation on the process of how to do image customization in simplestreams: TODO - [serge-hallyn] triage libvirt bugs: TODO - [serge-hallyn] go over high prio libvirt bugs: TODO + [serge-hallyn] triage libvirt bugs: DONE + [serge-hallyn] go over high prio libvirt bugs: INPROGRESS Work items for ubuntu-14.10: [serge-hallyn] discuss cgmanager features through systemd/cgfs (plumbers): POSTPONED determine ssd caching solution (bcache is it): DONE investigate support of ruby for puppet: TODO -- General server work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-server-core -- 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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO [tycho-s] (or serge-hallyn) design lxc-restart: TODO [tycho-s] criu: hook the network interface up at restart: TODO [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: TODO [serge-hallyn] (actually hazmat) image based workflow for juju: TODO [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED [tycho-s] c/r consoles : TODO [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO Work items for ubuntu-14.09: [serge-hallyn] design security profiles: TODO [serge-hallyn] Investigate the syslog namespace and try to get things forward a bit (1d): TODO - [serge-hallyn] (or sforshee) test mounts in unprivileged containers, perhaps using mountlo: TODO + [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: TODO -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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
Re: [Bug 1368439] [NEW] Random high latency with KSM enabled and multiple CPU sockets
affects: linux ** Also affects: linux Importance: Undecided Status: New -- 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/1368439 Title: Random high latency with KSM enabled and multiple CPU sockets To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1368439/+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 1368439] Re: Random high latency with KSM enabled and multiple CPU sockets
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux -- 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/1368439 Title: Random high latency with KSM enabled and multiple CPU sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368439/+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
Re: [Bug 1324174] Re: qemu should attempt to re-load kvm_intel to enable nesting at first install
Sadly this fix isn't quite right. The reason is that the modprobe file is qemu-system-x86.modprobe, but the postinst doing the reload of kvm_intel is qemu-system-common.postinst. -- 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/1324174 Title: qemu should attempt to re-load kvm_intel to enable nesting at first install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1324174/+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 1324174] Re: qemu should attempt to re-load kvm_intel to enable nesting at first install
I've 'fixed' the fix in utopic, so can post a new fix to trusty once 2.0.0+dfsg-2ubuntu1.4 is kicked out of the archive. ** Tags removed: verification-needed ** Tags added: verification-failed -- 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/1324174 Title: qemu should attempt to re-load kvm_intel to enable nesting at first install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1324174/+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 1367730] Re: container root directory has broken permissions with tight umask and --keep-data
Thanks. Meanwhile I've raised the issue on lxc-devel mailing list. -- 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/1367730 Title: container root directory has broken permissions with tight umask and --keep-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367730/+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 1368233] Re: package qemu-system-misc 2.0.0+dfsg-2ubuntu1.2 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu-system-microblazeel' to '/usr/bin/qemu-system-microblazeel.dp
It appears your local copy of the package is corrupted: Unpacking qemu-system-misc (2.0.0+dfsg-2ubuntu1.3) over (2.0.0+dfsg-2ubuntu1.2) ... dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt Please try the following: sudo apt-get clean sudo apt-get update sudo apt-get install -f and let us know whether that fixes the problem for you. ** 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/1368233 Title: package qemu-system-misc 2.0.0+dfsg-2ubuntu1.2 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu- system-microblazeel' to '/usr/bin/qemu-system-microblazeel.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1368233/+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 1310919] Re: pam_winbind krb5_ccache_type=FILE stopped working after 14.04 upgrade
Thanks @msaxl, I'll add this patch to our package. ** Changed in: samba (Ubuntu Utopic) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1310919 Title: pam_winbind krb5_ccache_type=FILE stopped working after 14.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1310919/+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 1365947] Re: 'virsh migrate' fails in a password authentication of SSH
Thanks. so those should be fixed in the 1.2.8 version we are trying to upload (awaiting FFE) to utopic now. Note also that commit 7eabd55. introduced a regression fixed by c285ffc4. We can SRU these into trusty once they are in utopic. ** Also affects: libvirt (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1365947 Title: 'virsh migrate' fails in a password authentication of SSH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1365947/+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 1355966] Re: [FFE] Implement AbandonScope (etc)
** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Changed in: cgmanager (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: [FFE] Implement AbandonScope (etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1355966/+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 1355966] Re: [FFE] Implement AbandonScope (etc)
** Changed in: cgmanager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: [FFE] Implement AbandonScope (etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1355966/+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 1367495] Re: Bridge still not created if bind9 is on
Thanks for reporting this bug. I'm not sure it's actually a dup of 1240757, because the syslog seems to indicate that dnsmasq is offering addresses over lxcbr0. Could you do 'lxc-start -n container0 -l trace -o debug.out' and attach debug.out here? ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+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 1367730] Re: container root directory has broken permissions with tight umask and --keep-data
** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1367730 Title: container root directory has broken permissions with tight umask and --keep-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367730/+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 1310919] Re: pam_winbind krb5_ccache_type=FILE stopped working after 14.04 upgrade
It looks like the patch was accidentally dropped from series two merges ago, and in the last merge was dropped for not being in series. However, the deeper problem is that the patch hasn't made it upstream. Looking at the upstream bug, in fact, the proposed fix has changed a bit. Would someone care to test a package with the last patch from https://bugzilla.samba.org/show_bug.cgi?id=10490 and, if that still works, try to push the samba bug along? Please report here if that patch does work and I will push the patch into our samba package and raise a debian bug to do the same. ** Changed in: samba (Ubuntu Utopic) Status: Fix Released = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1310919 Title: pam_winbind krb5_ccache_type=FILE stopped working after 14.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1310919/+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 1366868] Re: kvm: dompmwakeup fails if domain becomes pmsuspended
Thanks, we can combine this SRU with bug 1324174. -- 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/1366868 Title: kvm: dompmwakeup fails if domain becomes pmsuspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1366868/+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 1367422] [NEW] [FFE] Upgrade to 1.2.8
Public bug reported: The lastest libvirt release is 1.2.8. This includes a number of bugfixes and memory leaks since 1.2.6. Uploading this to Utopic will make backporting of bug-fixes in SRUs easier. The lp:qa-regression-testing scripts/test-libvirt.py has been run against this package, showing only the following to failures (which appear to be due to virt-install changes) == FAIL: test_virt_install_cdrom (__main__.LibvirtTestVirtinst) Test virt-install --cdrom -- Traceback (most recent call last): File ./test-libvirt.py, line 1241, in test_virt_install_cdrom self.assertTrue(s in report, result + report) AssertionError: Could not find 'Creating storage' in: WARNING /tmp/tmpQSxt2f/qatest-virtinst.img may not be accessible by the hypervisor. You will need to grant the 'libvirt-qemu' user search permissions for the following directories: ['/tmp/tmpQSxt2f'] WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. Starting install... Allocating 'qatest-virtinst.img' | 10 MB 00:00 Creating domain... |0 B 00:00 Domain installation still in progress. You can reconnect to the console to complete the installation process. == FAIL: test_virt_install_location (__main__.LibvirtTestVirtinst) Test virt-install --location -- Traceback (most recent call last): File ./test-libvirt.py, line 1333, in test_virt_install_location self.assertTrue(s in report, result + report) AssertionError: Could not find 'Creating domain' in: WARNING No 'console' seen in --extra-args, a 'console=ttyS0' kernel argument is likely required to see text install output from the guest. Starting install... Retrieving file MANIFEST... | 1.7 kB 00:00 ... Retrieving file MANIFEST... | 1.7 kB 00:00 ... Retrieving file linux... | 7.7 MB 00:00 ... Retrieving file initrd.gz... | 16 MB 00:00 ... Allocating 'qatest-virtinst.qcow2' | 10 MB 00:00 ERRORinternal error: process exited while connecting to monitor: qemu: could not load kernel '/home/serge/.cache/virt-manager/boot/virtinst-linux.Dqu1zu': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///session start qatest-virtinst otherwise, please restart your installation. Installing into a VM from my ppa (where it is called ~ppa2), I get: serge@us1:/etc/apparmor.d/libvirt$ sudo apt-get install libvirt-bin Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: at-spi2-core colord colord-data dconf-gsettings-backend dconf-service fontconfig hicolor-icon-theme libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libcairo-gobject2 libcairo2 libcolord2 libcolorhug2 libcups2 libdatrie1 libdconf1 libexif12 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgphoto2-6 libgphoto2-l10n libgphoto2-port10 libgraphite2-3 libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk-vnc-2.0-0 libgudev-1.0-0 libgusb2 libgvnc-1.0-0 libharfbuzz0b libieee1284-3 libjasper1 libjbig0 liblcms2-2 libltdl7 libmirclient8 libmirclientplatform-mesa libmircommon1 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libprotobuf8 libpulse-mainloop-glib0 libsane libsane-common libspice-client-glib-2.0-8 libspice-client-gtk-3.0-4 libthai-data libthai0 libtiff5 libusbredirhost1 libv4l-0 libv4lconvert0 libvpx1 libwayland-client0 libwayland-cursor0 libxcb-render0 libxcb-shm0 libxcomposite1 libxcursor1 libxi6 libxinerama1 libxkbcommon0 libxpm4 libxrandr2 libxtst6 python-libxml2 python-urlgrabber spice-client-glib-usb-acl-helper Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libvirt0 Suggested packages: radvd lvm2 The following NEW packages will be installed: libvirt-bin libvirt0 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/7,255 kB of archives. After this operation, 18.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package libvirt0. (Reading database ... 64402 files and directories currently installed.) Preparing to unpack .../libvirt0_1.2.8-0ubuntu1~ppa2_amd64.deb ... Unpacking libvirt0 (1.2.8-0ubuntu1~ppa2) ... Selecting previously unselected package libvirt-bin. Preparing to unpack .../libvirt-bin_1.2.8-0ubuntu1~ppa2_amd64.deb ... Unpacking
[Bug 1287841] Re: FFE: libvirt-python 1.2.2
** Changed in: libvirt-python (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt-python in Ubuntu. https://bugs.launchpad.net/bugs/1287841 Title: FFE: libvirt-python 1.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1287841/+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 1367425] [NEW] [FFE] Upgrade to 1.2.8
Public bug reported:
This will be needed for libvirt-python to match libvirt if the libvirt
FFE for 1.2.8 (bug 1367422) is approved.
The changelog follows:
2014-09-01 Pavel Hrdina phrd...@redhat.com
Implement API bindings for virDomainBlockCopy
2014-09-01 Pavel Hrdina phrd...@redhat.com
API: Implement bindings for virDomainListGetStats
Implement the function by returning a list of tuples instead the array
of virDomainStatsRecords and store the typed parameters as dict.
2014-09-01 Peter Krempa pkre...@redhat.com
API: Implement bindings for virConnectGetAllDomainStats
Implement the function by returning a list of tuples instead the array
of virDomainStatsRecords and store the typed parameters as dict.
2014-09-01 Peter Krempa pkre...@redhat.com
API: Skip 'virDomainStatsRecordListFree'
The new API function doesn't make sense to be exported in python. The
bindings will return native types instead of the struct array.
2014-09-01 Pavel Hrdina phrd...@redhat.com
generator: resolve one level of enum reference
In the libvirt.h we have one enum defined by references from another
enum and it leads in wrong order of definitons in python code. To
prevent this we should resolve that references before we generate the
python code.
For now we have only one level of references so we will count with that
in the generator but we should update it in the future to be more
flexible.
2014-08-19 Mo Yuxiang moyuxi...@huawei.com
build: Fix build warning on libvirt-python
On compiling libvirt-python, we get such a warning:
libvirt-qemu-override.c: In function
‘libvirt_qemu_virConnectDomainQemuMonitorEventRegister’:
libvirt-qemu-override.c:304: warning: suggest explicit braces to avoid
ambiguous ‘else’
Py_DECREF is a macro using if/else on older Python releases.
The solution is to add braces.
Python 2.7 and newer has the macro wrapped in a do { } while(0) block.
2014-08-11 Zhou Yimin zhouyi...@huawei.com
Fix libvirt_longlongWrap returning a very large value
If hypervisor is not Xen, the errs in struct _virDomainBlockStats will be
-1.
But in KVM when we call domain.blockStats(), errs is 18446744073709551615.
To fix that, this patch has two changes:
1. Replace use of the PyLong_FromUnsignedLongLong with PyLong_FromLongLong
in function libvirt_longlongWrap
2. If the paramemter of libvirt_longlongWrap is unsigned long long,
use libvirt_ulonglongWrap instead because of above change.
After this patch, errs is -1 which is consistent with virDomainBlockStats
api.
2014-08-04 Eric Blake ebl...@redhat.com
maint: document use of libvirt's run script
Ever since libvirt commit 78c09530, it's easier to just use the
run script.
* README: Mention run script.
2014-08-04 Eric Blake ebl...@redhat.com
Bump version to 1.2.8 for new dev cycle
2014-07-29 Jiri Denemark jiri.denem...@gmail.com
spec: Reorganize to satisfy buggy spectool
spectool parses a specfile and strips everything but a preamble.
However, if the first section is preceded by %if clause, it keeps it
there which then makes rpmbuild complain about unmatched %if. Let's make
the buggy tool happy by moving sections around so that the first one is
not in any conditional.
2014-07-22 Martin Kletzander mklet...@redhat.com
Bump version to 1.2.7 for new dev cycle
** Affects: libvirt-python (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt-python in Ubuntu.
https://bugs.launchpad.net/bugs/1367425
Title:
[FFE] Upgrade to 1.2.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1367425/+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 1324174] Re: qemu should attempt to re-load kvm_intel to enable nesting at first install
** Description changed: - Otherwise user may be confused as to why nesting is not enabled until a + Otherwise user may be confused as to why nesting is not enabled until a reboot. + + SRU Justification: + 1. Impact: Users who install a new intel-baesd machine and immediately start + a VM will not be able to start nested VMs. + 2. Development fix: reload kvm_intel when qemu is installed, if nesting was + not yet enabled + 3. Stable fix: same as development fix + 4. Test case: Set up a new trusty host. install qemu-kvm. (do not reboot) + create a vm, and in that vm try to start another kvm vm. + 5. Regression potential: We only unload and reload the kvm_intel module if + nesting was not already enabled. This should cause no regression. -- 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/1324174 Title: qemu should attempt to re-load kvm_intel to enable nesting at first install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1324174/+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
[Blueprint servercloud-u-server-core] General server work for Utopic
Blueprint changed by Serge Hallyn: Work items changed: Work items for ubuntu-14.06: [serge-hallyn] convert libvirt to cgmanager (4d): DONE [racb] Early cycle merge report: POSTPONED [serge-hallyn] merge qemu: DONE Work items for ubuntu-14.07: [serge-hallyn] cgmanager package into debian: DONE [serge-hallyn] systemd-shim integration for cgmanager: DONE [jamespage] (with raharper) docker 1.0 in 14.04: INPROGRESS Work items for ubuntu-14.08: [racb] Late cycle merge report: TODO [smoser] add simplestreams data to ubuntu core images: TODO [serge-hallyn] triage qemu bugs: DONE - [serge-hallyn] provide cgmanager features through systemd: INPROGRESS [serge-hallyn] go over high prio qemu bugs: DONE [racb] bcache in universe: TODO [racb] add scribe (https://github.com/facebook/scribe) to universe: POSTPONED [racb] add meteor (https://github.com/meteor/meteor) to universe: POSTPONED Work items for ubuntu-14.09: [smoser] write documentation on the process of how to do image customization in simplestreams: TODO [serge-hallyn] triage libvirt bugs: TODO [serge-hallyn] go over high prio libvirt bugs: TODO Work items for ubuntu-14.10: + [serge-hallyn] discuss cgmanager features through systemd/cgfs (plumbers): POSTPONED determine ssd caching solution (bcache is it): DONE investigate support of ruby for puppet: TODO -- General server work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-server-core -- 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
Re: [Bug 1365163] Re: qemu-system-x86_64 crashed with SIGABRT in spice_logv()
This is interesting. The apparmor policy includes the rule: owner /run/shm/spice.* rw /dev/shm is a symlink to /run/shm, so you should have the needed permissions. Could you please show the results of ls -ld /run/shm /dev/shm ls -l /run/shm /dev/shm status: incomplete ** 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/1365163 Title: apparmor breaks virt-manager creation [qemu-system-x86_64 crashed with SIGABRT in spice_logv()] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1365163/+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 1365163] Re: apparmor breaks virt-manager creation [qemu-system-x86_64 crashed with SIGABRT in spice_logv()]
Fascinating - thanks. So we should double up on those rules. ** Changed in: qemu (Ubuntu) Status: New = Triaged ** Summary changed: - apparmor breaks virt-manager creation [qemu-system-x86_64 crashed with SIGABRT in spice_logv()] + libvirt-qemu profile needs /dev/shm/spice-* rule for systemd hosts. -- 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/1365163 Title: libvirt-qemu profile needs /dev/shm/spice-* rule for systemd hosts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1365163/+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 1365163] Re: libvirt-qemu profile needs /dev/shm/spice-* rule for systemd hosts.
** Package changed: qemu (Ubuntu) = libvirt (Ubuntu) -- 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/1365163 Title: libvirt-qemu profile needs /dev/shm/spice-* rule for systemd hosts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1365163/+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 1287840] Re: FFE: libvirt-1.2.2
** 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/1287840 Title: FFE: libvirt-1.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1287840/+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
Re: [Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
There are 69 commits to block/qcow* between 1.5.0 and 1.7.0. I have compiled binaries of qemu-system-x86_64 and qemu-img at each of those commits and pushed them to http://people.canonical.com/~serge/binaries.0 through http://people.canonical.com/~serge/binaries.68 Note that binaries.0 is the *latest* commit. So to bisect with these you could start with binaries.34, then if that shows corruption, try binaries.51, or if it does not, try binaries.17 etc. 6 steps should get us to a single commit. It's not certain that one of these commits caused the regression, but it seems a reasonable place to start. -- 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/1292234 Title: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+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 1362224] Re: lxc-clone does not randomize MAC address - juju-local machines have same IPs
*** This bug is a duplicate of bug 1346815 *** https://bugs.launchpad.net/bugs/1346815 ** This bug has been marked a duplicate of bug 1346815 lxc-clone causes duplicate MAC address and IP address -- 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/1362224 Title: lxc-clone does not randomize MAC address - juju-local machines have same IPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1362224/+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 1363063] Re: ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1
** Changed in: qemu-kvm (Ubuntu) Status: New = 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/1363063 Title: ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1363063/+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
Re: [Bug 1350947] Re: apparmor: no working rule to allow making a mount private
affects: apparmor ** Also affects: apparmor 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. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+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
Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
@Raphi, You say you started the instance with -machine pc-1.0. To accept incoming migration from precise you must use -machine pc-1.0-qemu-kvm -- 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/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1361976] Re: LXC 1.0.5-0ubuntu0 is uninstallable
Please show us the contents of /var/log/apt/term.log, /etc/lsb-release, /etc/lxc/lxc-net.conf, /etc/default/lxc*, /usr/sbin/policy-rc.d, and the results of 'uname -a', 'dpkg -l | grep lxc', and 'ls -l /sbin/init'. ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1361976 Title: LXC 1.0.5-0ubuntu0 is uninstallable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1361976/+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 1347020] Re: trusty host - utopic lxc container cloudimage boot with systemd does not work
** Changed in: lxc (Ubuntu) Status: New = Confirmed ** 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/1347020 Title: trusty host - utopic lxc container cloudimage boot with systemd does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+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 1358268] Re: ppc64le (+ ppcle) magic is missing in debian/binfmt-update-in
On the qemu-ppc and qemu-devel mailing lists the following query was made about the non-packaging changes: So before we add anything to QEMU, I would like to first see someone point me to kernel patches that actually enable LE on Linux for 32bit user space. So far I'm not aware of any (and I doubt it makes much sense) In the original description you had said I am in the porting powerpcel (32bit ppc LE) ubuntu 14.04, and got successfully chroot with this qemu-ppcle patch and it looks very promising (i.e. build perl looks ok) To be sure I am understanding you right, are you in fact working on the kernel patches that would be needed for this to be useful? -- 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/1358268 Title: ppc64le (+ ppcle) magic is missing in debian/binfmt-update-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268/+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 1347020] Re: trusty host - utopic lxc container cloudimage boot with systemd does not work
Please make sure that lxc.kmsg = 0 in your container configuration file for systemd guests. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: trusty host - utopic lxc container cloudimage boot with systemd does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1347020/+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 1358268] Re: ppc64le (+ ppcle) magic is missing in debian/binfmt-update-in
Thanks for submitting this patch. I'll aim to get it into 14.10 and 14.04. Is there a particular way you'd recommend testing this, or should i simply download the ppc64le 14.10 cd image and try chrooting into it? ** 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/1358268 Title: ppc64le (+ ppcle) magic is missing in debian/binfmt-update-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268/+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
Re: [Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Hi Jamie, just to make sure, did you permanently disable ksm? Does cat /sys/kernel/mm/ksm/run still show 0? I've so far never seen a case where a reboot did not fix the issue, nor have I seen an issue (other than suspending the host sometimes causing the VM to hang so that I have to destroy it) with ksm disabled. I had hoped to do some large parallel upgrade tests this week, but network at linuxcon is not up to the task (even with apt-cacher-ng!) If I can find a better room I'll see about trying there. -- 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/1292234 Title: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+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
Re: [Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Ok - thanks Jamie. -- 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/1292234 Title: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+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 1358405] Re: cannot execute binary /usr/bin/kvm-img: No such file or directory
libvirt searches at startup for one of the kvm-img and qemu-img commands. If the kvm-img command goes away while libvirt is running, then it continues to try to use kvm-img, and this error occurs. Restarting libvirt is therefore a workaround. The kvm-img command has not existed since early in the trusty cycle. On a precise-to-trusty upgrade, libvirt will be restarted (preventing this error from being seen). The reason you saw it was that yo uupgraded from the saucy version, which is no longer spuported. I'll therefore mark this bug invalid. We could otherwise handle it by having qemu updates always cause a libvirt restart, but i don't believe that's warranted. ** Changed in: libvirt (Ubuntu) Status: New = Invalid -- 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/1358405 Title: cannot execute binary /usr/bin/kvm-img: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1358405/+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 1261338] Re: lxc-stop and even lxc-stop -k can hang
** Changed in: lxc (Ubuntu) Status: Incomplete = New -- 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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
Re: [Bug 1357103] Re: apparmor denied a golang build inside a container
@Andreas, yes that's definately what it sounds like. -- 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/1357103 Title: apparmor denied a golang build inside a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1357103/+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 1350435] Re: tcg.c:1693: tcg fatal error
Perhaps i don't understand what you are doing. My understanding was that a package is being built (in the buildds) under qemu. Qemu is failing due to tcg failure. We want to tes twhether a qemu patch fixes it. That's why I suggest installing the new qemu package on your host, using it to run a new server VM, and building the problematic package inside that VM. That way we can see whether the proposed qemu package fixes the build error. -- 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/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+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 1261338] Re: lxc-stop and even lxc-stop -k can hang
Thanks for the information. Indeed, lxc-stop -k still works by talking to the lxc monitor. What appears to have happened here is that the monitor itself is frozen. Could you please show full output of: ps -ef Then do 'ps -ef | grep lxc-start' to find the lxc-start process for the hung container. In one terminal do sudo strace -f -odebug.out -p $pid where $pid is the process id of the lxc-start. Then in another terminal again do lxc-stop -n $container -k and attach the file debug.out to this report. ** Changed in: lxc (Ubuntu) Status: Invalid = Incomplete -- 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
Hi James, does setting lxc.network.mtu = 9000 in the container configuration file work? Depending on how juju creates the containers, you may be able to simply add that line to the bottom of /etc/lxc/default.conf to get the desired result. -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1289527] Re: qemu-aarch64-static: java dies with SIGILL
Hi Dann, yeah, thanks - let's mark this fixed and open a new one. ** Changed in: qemu Status: New = Fix Released ** Changed in: qemu (Ubuntu) Status: Incomplete = 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/1289527 Title: qemu-aarch64-static: java dies with SIGILL To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289527/+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
