[Bug 1413922] Re: lxc unprivileged containers broken
Hi Serge, Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james: /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope' allowed me to start the non-priv container. ** 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/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1413922] Re: lxc unprivileged containers broken
Ah - seems we'd actually need to add in a couple of loops in those original dep-8 tests: run the tests as root, then run as a non-priv user too! :) -- 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/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1413922] [NEW] lxc unprivileged containers broken
Public bug reported: Seems to be due to 1.1.0~rc1-0ubuntu1 landing? $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug lxc-start: lxc_start.c: main: 345 The container failed to start. lxc-start: lxc_start.c: main: 347 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 349 Additional information can be obtained by setting the --logfile and --logpriority options. lxc.log attached. On a related note, it seems that the dep8 tests I originally wrote for lxc [1] have been replaced to call lxc's own test suite. However, whereas these new tests are somehow passing in jenkins [2], I belied the crude tests in [1] would have caught this issue as they actually call the command-line tools users run. Could we maybe bring back [1] and run both sets of tests to avoid such a regression in future? [1] - https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938 [2] - https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 09:15:29 2015 InstallationDate: Installed on 2014-04-11 (286 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid ** Attachment added: "lxc.log" https://bugs.launchpad.net/bugs/1413922/+attachment/4304130/+files/lxc.log -- 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/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1396497] [NEW] 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot
Public bug reported: qemu-img _may_ be working as designed, but it feels like this could be a bug. I'd certainly prefer to only allow unique snapshot names (unless maybe something like a "--force-non-unique-snapshot-names" was also specified). If this really is correct behaviour, it should be documented as qemu- img(1) currently specifies no details whatsoever regarding expected behaviour or valid snapshot names. $ qemu-img snapshot -l image.cow $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow $ Note also how snapshot deletion works in reverse order - the oldest snapshot with a given name is deleted first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 2.1+dfsg-4ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 26 08:28:16 2014 InstallationDate: Installed on 2014-04-11 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 719 2 0.0 [kvm-irqfd-clean] MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to vivid on 2014-05-08 (201 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1396497 Title: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1396497/+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 1383433] Re: please package the cloud-init ci-tool
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1383433 Title: please package the cloud-init ci-tool To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1383433/+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] [NEW] install failure under systemd
Public bug reported: Setting up lxc (1.1.0~alpha1-0ubuntu5) ... Failed to issue method call: Unit lxc.service failed to load: No such file or directory. invoke-rc.d: initscript lxc, action "start" failed. dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 6 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1376717 Title: install failure 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 1357252] Re: upstart can race with cgmanager when using remove-on-empty
** Changed in: upstart Status: In Progress => Fix Released ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart (Ubuntu) Status: New => 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/1357252 Title: upstart can race with cgmanager when using remove-on-empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: upstart can race with cgmanager when using remove-on-empty
** Summary changed: - systemd-shim fails to handle cgmanager being unavailable + upstart can race with cgmanager when using remove-on-empty ** Changed in: upstart Status: Invalid => In Progress -- 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/1357252 Title: upstart can race with cgmanager when using remove-on-empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Changed in: upstart Status: In Progress => Invalid ** Changed in: upstart Importance: Critical => Undecided -- 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/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Also affects: systemd-shim (Ubuntu) Importance: Undecided Status: New -- 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/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** No longer affects: linux (Ubuntu) -- 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/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Changed in: upstart Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: "Application failed to start." during autopilot tests after the newest ubuntu-app-launch landing
** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New -- 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/1357252 Title: "Application failed to start." during autopilot tests after the newest ubuntu-app-launch landing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1314697] Re: DNS resolution no longer works; dnsmasq uses 100% CPU
A bit of debugging shows that the culprit is blockdata_expand() which is being called via blockdata_init(). The issue seems to be that blockdata_expand() is passed a parameter of zero. That function then mallocs zero bytes (successfully seemingly), the proceeds to overwrite data before the returned address resulting the the 2 fds being set to zero. blockdata_expand() is passed zero since daemon->cachesize (aka dnsmasq_daemon->cachesize) is zero. This is confirmed by looking at syslog which shows: May 8 21:56:54 utopic dnsmasq[10812]: started, version 2.70 cache disabled -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: DNS resolution no longer works; dnsmasq uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1314697] Re: DNS resolution no longer works; dnsmasq uses 100% CPU
BTW - the problem is recreatable for me every time simply by spinning up a utopic kvm instance. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: DNS resolution no longer works; dnsmasq uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1314697] Re: DNS resolution no longer works; dnsmasq uses 100% CPU
Updated description since problem is unrelated to upgrade - it just occurs with the version of dnsmasq currently in utopic. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: DNS resolution no longer works; dnsmasq uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1314697] Re: Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
Attached is a full strace from dnsmasq startup showing the problem. ** Attachment added: "dnsmasq-strace.log" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+attachment/4107998/+files/dnsmasq-strace.log ** Summary changed: - Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU + DNS resolution no longer works; dnsmasq uses 100% CPU -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: DNS resolution no longer works; dnsmasq uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1317444] [NEW] dnsmasq spins at 100% cpu trying to receive socket messages via stdin
Public bug reported: dnsmasq is spinning at 100% CPU. This also causes networking to fail. Problem seems to be that it is calling recvmsg(STDIN_FILENO, ...) which is totally invalid. See attached strace log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dnsmasq-base 2.70-1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 8 10:33:54 2014 InstallationDate: Installed on 2014-05-06 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140505) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "dnsmasq-strace.log" https://bugs.launchpad.net/bugs/1317444/+attachment/4107952/+files/dnsmasq-strace.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1317444 Title: dnsmasq spins at 100% cpu trying to receive socket messages via stdin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1317444/+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 1309810] Re: package cgroup-lite 1.9 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 100
*** This bug is a duplicate of bug 901038 *** https://bugs.launchpad.net/bugs/901038 Hi Serge, The problem I believe is that Upstart is in the process of restarting so initctl cannot (yet) reconnect to Upstart until it has finished the re- exec. See comment #7 on bug 901038. ** This bug has been marked a duplicate of bug 901038 packages fail to install: Failed to connect to socket /com/ubuntu/upstart: Connection refused -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1309810 Title: package cgroup-lite 1.9 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1309810/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
Hi Serge, I'm running on pure amd64 too so the problem is not arch-specific. The simplest way to recreate: $ kvm -cdrom /usr/lib/memtest86+/memtest86+.iso -m 512 Just hold down control+alt and frantically toggle the monitor using the '2' and '1'. Within a couple of seconds it hangs. -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1257352/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
Sorry - ignore that. However, problem persists on a separate fully- updated amd64 trusty system running kvm version 2.0.0~rc1+dfsg-0ubuntu3. -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1257352/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Right. So to be completely clear, by calling nih_dbus_setup(), nih was registering a libdbus handler that runs on the client side such that whenever libdbus deemed necessary, it would attempt to wake up the clients main loop by calling nih_main_loop_interrupt(). However, since the client didn't have an nih main loop, the interrupt pipe was never drained and eventually filled leading to the EAGAIN tight loop. Yes, I agree - maybe it should have been called nih_dbus_main_loop_setup() to make its usage clearer. -- 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
HI Serge - yes, problem is still there with the ppa versions: $ dpkg -l|egrep "kvm|qemu" ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1 all PXE boot firmware - ROM images for qemu ii kvm-ipxe 1.0.0+git-2013.c3d1e78-2ubuntu1 all transitional dummy package ii kvm-pxe 5.4.5 all Meta package providing kvm pxe-boot ROMs. ii qemu-common 2.0~git-20140320.71461b0-0ubuntu1 all dummy transitional package from qemu-common to qemu-keymaps ii qemu-keymaps 2.0~git-20140320.71461b0-0ubuntu1 all QEMU keyboard maps ii qemu-kvm 2.0~git-20140320.71461b0-0ubuntu1 i386 QEMU Full virtualization on x86 hardware (transitional package) ii qemu-kvm-extras-static 1.2.0-2012.09-0ubuntu2 all QEMU static user mode emulation binaries (transitional package) ii qemu-system 2.0~git-20140320.71461b0-0ubuntu1 i386 QEMU full system emulation binaries ii qemu-system-arm 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (arm) ii qemu-system-common 2.0~git-20140320.71461b0-0ubuntu1 i386 QEMU full system emulation binaries (common files) ii qemu-system-mips 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (mips) ii qemu-system-misc 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (miscelaneous) ii qemu-system-ppc 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (ppc) ii qemu-system-sparc 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (sparc) ii qemu-system-x86 1.7.0+dfsg-3ubuntu7 i386 QEMU full system emulation binaries (x86) ii qemu-user-static 2.0~git-20140320.71461b0-0ubuntu1 i386 QEMU user mode emulation binaries (static version) ii qemu-utils 2.0~git-20140320.71461b0-0ubuntu1 i386 QEMU utilities -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1257352/+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 1294200] Re: test linked against nih-dbus-tool-generated libraryis not thread-safe
Hi Serge, Looking at nih's configure.ac, you actually want to use '--enable- threading' I think. I've never used this option and tbh wasn't even aware it was there. -- 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/1294200 Title: test linked against nih-dbus-tool-generated libraryis not thread-safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1294200/+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 1268906] Re: cpu soft lockup running kvm
Still a problem on 3.13.0-17-generic. -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1277466] Re: unprivileged containers fail to start with 1.0.0~beta4-0ubuntu1
The problem does seem to be an LXC bug. However, I can work around it by changing the perms on my home directory from 0750 to 0755. -- 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/1277466 Title: unprivileged containers fail to start with 1.0.0~beta4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277466/+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 1277466] [NEW] unprivileged containers fail to start with 1.0.0~beta4-0ubuntu1
Public bug reported: $ lxc-start -n trusty lxc_container: Permission denied - failed to get real path for '/home/james/.local/share/lxc/trusty/rootfs' lxc_container: failed to mount rootfs lxc_container: failed to setup rootfs for 'trusty' lxc_container: failed to setup the container lxc_container: invalid sequence number 1. expected 2 lxc_container: failed to spawn 'trusty' Downgrading to 1.0.0~beta3-0ubuntu1 fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Feb 7 11:15:30 2014 InstallationDate: Installed on 2010-10-21 (1205 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2013-11-01 (97 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 trusty -- 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/1277466 Title: unprivileged containers fail to start with 1.0.0~beta4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277466/+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 1268906] Re: cpu soft lockup running kvm
I think the switch to 3.13 may have borked kvm for me. I'll try to confirm that tomorrow... -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Latest trusty desktop image (dated 24 Jan) results in the oops when running with kvm as: $ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024 -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
To be clear, my host system is a 64-bit capable first-gen i7, but is actually running fully 32-bit. -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Same problem running with -vnc :7 ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Latest series of oopses running on a fully updated trusty system. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Serge has just identified that the trigger for this bug is running kvm with '-net user': without this option, no issues. ** Changed in: qemu-kvm (Ubuntu) Status: New => Confirmed -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1263738] Re: login console 0 in user namespace container is not configured right
** Changed in: upstart Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart Status: New => Fix Committed ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu Trusty) 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/1263738 Title: login console 0 in user namespace container is not configured right To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 1263738] Re: login console 0 in user namespace container is not configured right
@Serge - perfectly happy to change that, in fact... @Stéphane - could you review and test lp:~jamesodhunt/upstart/kmsg- noctty? Thanks! -- 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/1263738 Title: login console 0 in user namespace container is not configured right To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 1268906] Re: cpu soft lockup running kvm
dmesg from 3.13.0-5-generic kernel. ** Attachment added: "dmesg.3.13.0-5-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3954151/+files/dmesg.3.13.0-5-generic -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Still a problem on 3.13.0-5-generic. -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1263738] Re: login console 0 in user namespace container is not configured right
> I haven't been able to find where in upstart this is happening, but on the > kernel side I can tell that it's due to an open() without > O_NOCTTY. Upstart does not open /dev/console without O_NOCTTY afaics. Are you sure your kernel debug is showing pid 1 is doing this? -- 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/1263738 Title: login console 0 in user namespace container is not configured right To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 1268906] Re: cpu soft lockup running kvm
Same problem with 3.13.0-4-generic. Any progress on this? kvm is unusable due to this issue. ** Attachment added: "dmesg-3.13.0-4-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3952909/+files/dmesg-3.13.0-4-generic.txt -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Same problem with 3.13.0-4-generic. -- 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Alas, same issue using kernel 3.13.0-031300rc8-generic. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
See CurrentDmesg.txt for lots of errors such as: [ 1688.474887] Call Trace: [ 1688.474914] [] kvm_vcpu_ioctl+0x433/0x4d0 [kvm] [ 1688.474924] [] ? wake_up_state+0xf/0x20 [ 1688.474931] [] ? wake_futex+0x65/0x90 [ 1688.474937] [] ? futex_wake+0x13d/0x160 [ 1688.474942] [] ? do_futex+0xeb/0x660 [ 1688.474966] [] ? vcpu_put+0x30/0x30 [kvm] [ 1688.474972] [] do_vfs_ioctl+0x2e2/0x4d0 [ 1688.474977] [] ? tick_program_event+0x29/0x30 [ 1688.474983] [] ? hrtimer_interrupt+0x142/0x2b0 [ 1688.474988] [] ? SyS_futex+0x8c/0x140 [ 1688.474993] [] SyS_ioctl+0x60/0x80 [ 1688.475002] [] syscall_call+0x7/0xb [ 1688.475009] [] ? __ticket_unlock_slowpath+0x13/0x31 ** Also affects: qemu-kvm (Ubuntu) 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/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
Hi Serge, Yes, I get the hang on upstream too (HEAD e157b8fdd412d48eacfbb8c67d3d58780154faa3). -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
Hi Serge, 1.7.0+dfsg-2ubuntu2 still exhibits the problem I'm afraid. -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
I never saw the issue with saucy. Downgrading to 1.5.0+dfsg-3ubuntu5.1 certainly appears to have resolved the issue for me, so it's looking like a regression introduced by 1.6.0+dfsg-2ubuntu4. -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+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 1257352] [NEW] kvm hangs occasionally when switching out of the qemu console
Public bug reported: To recreate (although this does *NOT* fail most of the time alas): 1) press "ctrl-alt-2" to switch to the qemu console. 2) type say "sendkey ctrl-alt-f1" 3) press "ctrl-alt-1". Expected outcome: Switch to tty1 in the VM. Actual outcome: No switch to tty1 in the VM. and qemu console unresponsive to any keyboard input. Rather a vague problem description I'm afraid but this has happened to me 3 times recently. No crash and no excessive CPU is observed. I'll grab an strace when it happens again and attach... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 1.6.0+dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 3.12.0-4.12-generic 3.12.1 Uname: Linux 3.12.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Dec 3 15:41:40 2013 InstallationDate: Installed on 2010-10-21 (1139 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2013-11-01 (31 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+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 1257352] Re: kvm hangs occasionally when switching out of the qemu console
... as if by magic it hung again :) I managed to trigger it by toggling the following two key combos rapidly starting from within the qemu console: ctrl-alt-1 # switch to console (actually, we're already there, but ...) ctrl-alt-2 # switch out of console ** Attachment added: "kvm-strace.log.gz" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+attachment/3922127/+files/kvm-strace.log.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/1257352 Title: kvm hangs occasionally when switching out of the qemu console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257352/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
scp suffers the same issue, but interestingly, so seemingly does pscp which hangs indefinitely after successfully connecting and starting to send the data. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1254085] [NEW] ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
Public bug reported: ssh -vvv is failing for me where is a VPN system. VPN is configured and connected via network-manager. Last messages from ssh (hangs forever): debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY = Workaround = $ sudo apt-get install putty $ putty This works perfectly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.4p1-1 ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0 Uname: Linux 3.12.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Nov 22 15:37:18 2013 InstallationDate: Installed on 2010-10-21 (1128 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-9 libpam-sshN/A keychain 2.7.1-1 ssh-askpass-gnome 1:6.4p1-1 SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013 SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1235231] Re: ci-info: eth0 not reliable in latest saucy images
Upstart certainly changed, but none of the changes affect console handling. Could the kernel change be the culprit maybe? -- 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/1235231 Title: ci-info: eth0 not reliable in latest saucy images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Re #27, removing -nographic still causes the same lockup for me. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
'qemu -serial file:/tmp/kvm.log' Looks like an alternative to 'qemu -nographic >/tmp/kvm.log 2>&1'. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
The latest advice for running on Canonistack (kvm guest instance where nested=Y is to): - Only run on a 64-bit Canonistack guest instance. - Modify bin/prepare-testbed and bin/run-adt-test to start the autopkgtest VM using 'qemu-system-x86_64 -enable-kvm'. - Have the DEP8 test running inside the autopkgtest VM start its VM using 'qemu -enable-kvm'. Using the above but appending '-nographic >/tmp/kvm.log 2>&1' to each kvm command-line to allow console log capture results in the first created VM (the one created by prepare-testbed/bin/run-adt-test) locking up. Unfortunately, there is no output in kvm.log. I'll retry without '-nographic' as smb has noticed this seems to affect the stability of the overall kvm stack. Even if this does work, it is clearly not ideal to discard console output (unless there is another magic qemu option we can try?) -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Latest kernel panic (from 2nd-level guest) using following kernel versions: host: 3.11.0-1-generic (-2 causes problems for my graphics hardware atm) 1st-level guest: 3.11.0-2-generic 2nd-level guest: 3.11.0-2-generic ** Attachment added: "kvm.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3775059/+files/kvm.log -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
To recreate:
1) Follow instructions on internal wiki (page
"InformationInfrastructure/IS/CanonicalOpenstack") to create a keypair.
2) Create an guest instance:
$ keyname="${USER}_lcy01"
$ image=$(euca-describe-images|grep saucy|head -1|awk '{print $2}')
$ euca-run-instances -k $keyname -t m1.medium $image
3) Identify IP address and instance name ("i-"):
$ euca-describe-instances
4) ssh into system
5) Install required packages:
$ sudo apt-get -y install genisoimage linux-image-extra-virtual bzr
qemu-kvm qemu-utils
6) Setup groups
$ usermod -G kvm -a ubuntu
7) Logout and back in again to pick up kvm group membership.
8) Checkout bzr branch:
$ bzr branch lp:auto-package-testing
$ cd auto-package-testing
9) Apply patch on this bug to disable byobu and enable kvm logging (to
/tmp/kvm.log)
10) Run the following:
bin/prepare-testbed -r saucy -d i386
11) tail -f /tmp/kvm.log and wait for massive cpu usage and kernel spew
in /tmp/kvm.log.
12) Cleanup:
$ euca-terminate-instances i-
--
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/1208455
Title:
general protection fault running apt-get inside double nested kvm VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
The kernel BUG: above happens when running "bin/prepare-testbed -r saucy -d i386" from lp:auto-package-testing in canonistack: the kvm instance spins at ~200% CPU again. I modified bin/prepare-testbed slightly to log the output of the vm and disable byoubu. See attached. ** Patch added: "auto-package-testing.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3773462/+files/auto-package-testing.diff -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Now that 3.11 is out of proposed, we're seeing a different kernel failure, starting with run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.11.0-2-generic /boot/vmlinuz-3.11.0-2-generic Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.11.0-2-generic Found initrd image: /boot/initrd.img-3.11.0-2-generic Found memtest86+ image: /boot/memtest86+.bin [ 776.392144] BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:18758] [ 776.392144] CPU: 0 PID: 18758 Comm: modprobe Tainted: GF 3.11.0-2-generic #5-Ubuntu [ 776.432133] BUG: soft lockup - CPU#1 stuck for 23s! [systemd-udevd:333] [ 776.432133] CPU: 1 PID: 333 Comm: systemd-udevd Tainted: GF 3.11.0-2-generic #5-Ubuntu [ 776.432133] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 776.432133] task: f5f619c0 ti: f5f3c000 task.ti: f5f3c000 [ 776.432133] Stack: [ 776.432133] Call Trace: [ 776.432133] Code: 08 89 0c 24 89 f1 e8 16 fc ff ff e9 36 ff ff ff 90 55 ba 00 01 00 00 89 e5 f0 66 0f c1 10 0f b6 ce 38 d1 74 0d 8d 74 26 00 f3 90 <0f> b6 10 38 ca 75 f7 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 [ 776.392144] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 776.392144] task: f56919c0 ti: f5746000 task.ti: f5746000 ** Attachment added: "kvm.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3773460/+files/kvm.log -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
I got the panic again last night. This was running a 3.11 kernel for the host, but of course the 1st and 2nd level guests were still running 3.10 as 3.11 is still in -proposed. So, although it's possible to get a test run with (3.11, 3.10, 3.10) I really need to try running with (3.11, 3.11, 3.11) to see if this provides a reliable solution. ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed => In Progress -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Testing with linux-image-3.11.0-0-generic from -proposed with nested=Y in all 3 environments does appear to solve this issue. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Fresh kernel panic from 2nd-level nested VM running with host, 1st level and 2nd level all running with nested=1. ** Attachment added: "kvm.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3763650/+files/kvm.log -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM
What we know so far: - the issue is not related to cloud-init. - the very high CPU load was atleast partly caused by byobu bug 1208853. To disable byobu... === modified file 'bin/prepare-testbed' --- bin/prepare-testbed 2013-08-06 08:05:16 + +++ bin/prepare-testbed 2013-08-06 14:01:42 + @@ -227,7 +227,7 @@ apt_update: true apt_upgrade: true -byobu_by_default: system +byobu_by_default: disable packages: - eatmydata - smb/apw noticed that nested=1 for the kvm_intel driver was not being set in the 1st and 2nd level nested VMs but was being set on the host. However, forcing nested=1 on the host system, the autopkgtest system *and* the pristine nested VM (2nd-level nesting) does not stop the kernel panic. Now trying with linux-image-3.11.0-0-generic to see if that helps... ** No longer affects: cloud-init (Ubuntu) ** Summary changed: - general protection fault running apt-get inside nested kvm VM + general protection fault running apt-get inside double nested kvm VM -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM
High CPU may be cloud-init. Using todays server image, running 'prepare- testbed' spins the CPU at 200%. The end of the log shows: Aug 6 10:13:15 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running config-package-update-upgrade-install using lock () Aug 6 10:13:15 autopkgtest [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/sem/update_sources - wb: [420] 19 bytes Aug 6 10:13:15 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running update-sources using lock () Aug 6 10:13:15 autopkgtest [CLOUDINIT] util.py[DEBUG]: Running command ['apt-get', '--option=Dpkg::Options::=--force-confold', '--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--quiet', 'update'] with allowed return codes [0] (shell=False, capture=False) Aug 6 10:13:34 autopkgtest [CLOUDINIT] util.py[DEBUG]: Running command ['apt-get', '--option=Dpkg::Options::=--force-confold', '--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--quiet', 'dist-upgrade'] with allowed return codes [0] (shell=False, capture=False) Aug 6 10:13:36 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: update-sources already ran (freq=once-per-instance) Aug 6 10:13:36 autopkgtest [CLOUDINIT] util.py[DEBUG]: Running command ['apt-get', '--option=Dpkg::Options::=--force-confold', '--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--quiet', 'install', 'eatmydata', 'linux-image-generic', 'autopkgtest', 'dpkg-dev', 'pbuilder', 'bzr'] with allowed return codes [0] (shell=False, capture=False) 1680s before timeout 1620s before timeout 1560s before timeout 1500s before timeout 1440s before timeout 1380s before timeout 1320s before timeout ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM
Note that #4 was taken from a local nested kvm environment (not OpenStack). ** Summary changed: - general protection fault running apt-get inside nested kvm VM on OpenStack + general protection fault running apt-get inside nested kvm VM -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM on OpenStack
Kernel logs can be found on bug 1208509. -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM on OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM on OpenStack
** Attachment added: "Another general protection fault panic" https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1208455/+attachment/3761555/+files/kvm.log -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM on OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM on OpenStack
I'm suspecting an issue with nested=1... the nested VM does eventually boot but it takes many minutes to do so. At this point, the cpu usage of qemu-kvm drops to reasonable values. But if you ssh into the vm, the usage jumps up to ~200% again. To recreate: $ sudo apt-get install -y genisoimage linux-image-extra-virtual bzr qemu-kvm qemu-utils $ sudo usermod -G kvm -a ubuntu $ sudo modprobe kvm_intel nested=1 $ bzr branch lp:auto-package-testing $ cd auto-package-testing $ bin/prepare-testbed -r saucy -d i386 ... and observe ps output. -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM on OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside nested kvm VM on OpenStack
Attempting to repeat the dep8 test run in the same environment has so far resulted in the qemu-kvm binary consuming 200% CPU (recreated on multiple nodes). -- 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/1208455 Title: general protection fault running apt-get inside nested kvm VM on OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] [NEW] general protection fault running apt-get inside nested kvm VM on OpenStack
Public bug reported: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu-kvm (Ubuntu) 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/1208455 Title: general protection fault running apt-get inside nested kvm VM on OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1124384] Re: Configuration reload clears event that others jobs may be waiting on
The attached is a minimal fix for the problem that applies to lp:upstart. I've tested this in Scotts LXC test scenario with reload-configuration being called mid-boot and the system boots correctly. We still need to finish writing the tests for this fix - that work will have to be completed at the sprint next week. ** Patch added: "upstart-bug-1124384-minimal-fix.diff" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3654975/+files/upstart-bug-1124384-minimal-fix.diff ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+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 1171866] [NEW] lxc-stop ignores invalid container names
Public bug reported: $ sudo lxc-ls -1 oneiric precise raring raring-cloned sid $ sudo lxc-stop -n foo $ echo $? 0 lxc-stop should return 1 in the example above and display an error rather than silently failing and returning 0 to denote success. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Tue Apr 23 14:57:33 2013 InstallationDate: Installed on 2010-10-21 (915 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-12-20 (123 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 raring -- 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/1171866 Title: lxc-stop ignores invalid container names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1171866/+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 1124384] Re: reload-configuration can confuse upstart
I believe the problem here is that -- in the case where a JobClass has no running instances -- a reload is causing the original JobClass to be destroyed. That eventually leads to Event->blockers to reach zero (as a result of the JobClasses EventOperators being freed) causing the event to be destroyed. That behaviour is correct inasmuch as events are being destroyed when they should. What is not correct is that the reload results in all this happening *before* the newly-loaded JobClass gets a chance to increment Event->blockers to avoid the event being freed. -- 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/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+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 1171464] [NEW] lxc-execute fails with error "Failed to find an lxc-init"
Public bug reported: $ sudo lxc-info -n raring state: STOPPED pid:-1 $ sudo lxc-execute -n raring -- true lxc-execute: Failed to find an lxc-init lxc-execute: invalid sequence number 1. expected 4 lxc-execute: failed to spawn 'raring' $ dpkg -l lxc|grep lxc-init || echo not found not found $ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Mon Apr 22 14:32:05 2013 InstallationDate: Installed on 2010-10-21 (914 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-12-20 (122 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 raring -- 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/1171464 Title: lxc-execute fails with error "Failed to find an lxc-init" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1171464/+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 1166841] Re: lxc-create fails if LANG != en_GB.UTF-8
What about the C locale? This fails as well. Maybe the ubuntu template could check LANG. If not set, or not in $(locale -a) or /usr/share/i18n/SUPPORTED, revert to en_US.UTF-8? -- 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/1166841 Title: lxc-create fails if LANG != en_GB.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1166841/+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 1166870] [NEW] lxc-clone fails silently
Public bug reported: $ sudo lxc-clone -o old -n new $ echo $? 1 $ sudo bash /usr/bin/lxc-clone -o old -n new Tweaking configuration Copying rootfs... Updating rootfs... 'raring-cloned' created $ Problem appears to be missing "|| true" in LXC_PATH= assignment in /usr/share/lxc/lxc.functions: LXC_PATH=$(grep -v "^#" "$globalconf" 2>/dev/null | grep "[ \t]*lxcpath[ \t]*=") The above can fail due to running via 'set -e' so needs to be something like: LXC_PATH=$(grep -v "^#" "$globalconf" 2>/dev/null | grep "[ \t]*lxcpath[ \t]*=" || true) ** 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/1166870 Title: lxc-clone fails silently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1166870/+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 1166841] [NEW] lxc-create fails if LANG != en_GB.UTF-8
Public bug reported: If LANG is not 'en_GB.UTF-8', lxc-create fails: $ echo $LANG fr_CA.UTF8 $ sudo lxc-create -n foo -t ubuntu -- raring lxc-create: No config file specified, using the default config /etc/lxc/default.conf Checking cache download in /var/cache/lxc/raring/rootfs-i386 ... Copy /var/cache/lxc/raring/rootfs-i386 to /var/lib/lxc/foo/rootfs ... Copying rootfs to /var/lib/lxc/foo/rootfs ... lxc-create: failed to execute template 'ubuntu' lxc-create: aborted $ export LANG=C $ sudo lxc-create -n foo -t ubuntu -- raring lxc-create: No config file specified, using the default config /etc/lxc/default.conf Checking cache download in /var/cache/lxc/raring/rootfs-i386 ... Copy /var/cache/lxc/raring/rootfs-i386 to /var/lib/lxc/foo/rootfs ... Copying rootfs to /var/lib/lxc/foo/rootfs ... lxc-create: failed to execute template 'ubuntu' lxc-create: aborted $ export LANG=en_GB.UTF-8 lxc-create: No config file specified, using the default config /etc/lxc/default.conf Checking cache download in /var/cache/lxc/raring/rootfs-i386 ... Copy /var/cache/lxc/raring/rootfs-i386 to /var/lib/lxc/raring/rootfs ... Copying rootfs to /var/lib/lxc/raring/rootfs ... Generating locales... en_GB.UTF-8... done Generation complete. ## # The default user is 'ubuntu' with password 'ubuntu'! # Use the 'sudo' command to run tasks as root in the container. ## 'ubuntu' template installed 'raring' created ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1166841 Title: lxc-create fails if LANG != en_GB.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1166841/+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 1166841] Re: lxc-create fails if LANG != en_GB.UTF-8
Adding '-x' to the ubuntu template the problem is with locale-gen: + configure_ubuntu /var/lib/lxc/raring/rootfs raring raring + rootfs=/var/lib/lxc/raring/rootfs + hostname=raring + release=raring + cat + cat + cat + '[' '!' -f /var/lib/lxc/raring/rootfs/etc/init/container-detect.conf ']' + '[' -z '' ']' + chroot /var/lib/lxc/raring/rootfs useradd --create-home -s /bin/bash ubuntu + echo ubuntu:ubuntu + chroot /var/lib/lxc/raring/rootfs chpasswd + '[' -z fr_CA.UTF8 ']' + chroot /var/lib/lxc/raring/rootfs locale-gen fr_CA.UTF8 lxc-create: failed to execute template 'ubuntu' lxc-create: aborted -- 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/1166841 Title: lxc-create fails if LANG != en_GB.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1166841/+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 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
Please can you boot such a system with '--debug' and capture syslog / dmesg / console so we can try and work out what is happening here. -- 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/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1066144] Re: arguments to dbus_server_disconnect() were incorrect
@Paul: Please can you specify which packages are newly installed for your to see this issue? Is it reproducable on other systems for you? As mentioned, I do not see this problem on vanilla quantal system + the postfix package installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1066144 Title: arguments to dbus_server_disconnect() were incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1066144/+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 1066144] Re: arguments to dbus_server_disconnect() were incorrect
Not an upstart issue fwics. ** Package changed: upstart (Ubuntu) => postfix (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1066144 Title: arguments to dbus_server_disconnect() were incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1066144/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
** Changed in: upstart Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+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 1003888] Re: corrupted kernel messages being logged to syslog
Hi Serge - two corruptions in the host as mentioned above. -- 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/1003888 Title: corrupted kernel messages being logged to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1003888/+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 1003888] Re: corrupted kernel messages being logged to syslog
-- 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/1003888 Title: corrupted kernel messages being logged to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1003888/+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 1003888] [NEW] corrupted kernel messages being logged to syslog
Public bug reported: Running a i686 32-bit quantal container on a i686 32-bit precise host I'm seeing kernel message corruption in /var/log/syslog in the container: ___ May 24 10:41:04 localhost ntpdate[172]: adjust time server 91.189.94.4 offset 0. 001225 sec May 24 10:41:05 localhost kernel: [4.531 t0 oIv otr rsn ___ May 24 10:44:06 localhost ntpdate[199]: adjust time server 91.189.94.4 offset -0 .000260 sec May 24 10:44:08 localhost kernel: [11726.678703] vethKvdkPd: no IPv6 routers pre sent May 24 10:44:08 localhost kernel: [11726.934078] eth0: no IPv6 routers present May 24 10:44:26 localhost kernel: <>[1174.942 ye10 ui(37526584) pamr"EID prto=mu t no"aldfasmth ro=1 aet198poie"x-otie-eal"nm=/a/i/raaeddbgs"pd105cm=uedha"ftp=db gs rnm=nn"fas"w May 24 10:45:31 localhost kernel: .33]eyL:oP urpst<6>[11809.800093] ADDRCONF(NET DEV_CHANGE): veth3jQTu8: link becomes ready May 24 10:45:31 localhost kernel: [11809.800220] lxcbr0: port 1(veth3jQTu8) ente ring forwarding state May 24 10:45:31 localhost kernel: [11809.800265] lxcbr0: port 1(veth3jQTu8) ente ring forwarding state May 24 10:45:42 localhost kernel: [11820.506530] et0:n P6otsre May 24 10:45:46 localhost kernel: 684773]lcr:pr (ehjT8 neigfradn tt May 24 10:57:11 localhost james: hello from quantal lxc ___ The host has 2 examples: May 24 12:02:20 azul kernel: [11811.087590] type=1400 audit(1337856332.979:49): apparmor="DENIED" operation="moun" if=fie lg ac"err-3prn=97 rfl=lccnanrdfut ae"vrlbuedha/euf/ i=99 om"raaed sye"euf"scae"oe lg=r"h oIvrurpst<6>[12815.645687] device vethemBouM entered promiscuous mode May 24 12:02:20 azul kernel: [12815.64492]ADCN(EDVU) ehmoM iki o ed ___ May 24 12:02:24 azul ntpd[3197]: new interface(s) found: waking up resolver May 24 12:02:31 azul kernel: -fut ae"vrlbuedha/euf/ i=47 om"raaed sye"euf"scae"oe lg=r"ere May 24 12:05:01 azul CRON[25554]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) ___ Kernel version: $ uname -a Linux azul 3.2.0-24-generic-pae #38-Ubuntu SMP Tue May 1 16:40:26 UTC 2012 i686 i686 i386 GNU/Linux $ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu56 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Thu May 24 12:03:41 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_CA.UTF8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to precise on 2012-01-12 (132 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- 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/1003888 Title: corrupted kernel messages being logged to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1003888/+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 999187] Re: lxc-create for armhf fails with error "failed to execute template 'ubuntu'"
Hi Serge - yes, this was on a precise host. Confirmed that lxc 0.7.5-3ubuntu56 from precise-proposed/universe now allows me to create, start and stop an armhf container. Thanks for the quick turn-around! -- 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/999187 Title: lxc-create for armhf fails with error "failed to execute template 'ubuntu'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/999187/+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 999187] Re: lxc-create for armhf fails with error "failed to execute template 'ubuntu'"
** Attachment added: "lxc.log" https://bugs.launchpad.net/bugs/999187/+attachment/3146114/+files/lxc.log -- 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/999187 Title: lxc-create for armhf fails with error "failed to execute template 'ubuntu'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/999187/+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 999187] [NEW] lxc-create for armhf fails with error "failed to execute template 'ubuntu'"
Public bug reported: $ sudo lxc-create -n quantal-armhf -t ubuntu -- -a armhf : : W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. I: Configuring the base system... : : E: Unable to locate package mountall:amd64 E: Unable to locate package iproute:amd64 E: Unable to locate package isc-dhcp-client:amd64 failed to execute template 'ubuntu' aborted $ ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/999187 Title: lxc-create for armhf fails with error "failed to execute template 'ubuntu'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/999187/+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 931584] Re: Upstart should close all non-standard fds before starting a job
I agree with Steve here: Upstart is careful to set CLOEXEC on all the fds it has control over, so I would much prefer this be fixed at source. A temporary work-around for jobs that are affected by this issue is to add the following code at the top of all appropriate script sections - remember that all script and exec sections run as different processes so if you have a pre-start and a script section, the code below should be added to the top of *both* those sections: script # close unexpectedly open fds # The 'readlink' ensures we don't try to close the fd we're using to read the /proc/self/fd directory. for fd in /proc/self/fd/* do fd=$(basename $fd) case "$fd" in 0|1|2) ;; *) readlink $fd && eval "exec $fd>&-" || :;; esac done # << do something useful here >> end script -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/931584 Title: Upstart should close all non-standard fds before starting a job To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/931584/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
@Jason: thanks for the feedback. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
If you would like to help with testing the fix for this bug, I've put an updated version of Upstart (version '1.4-0ubuntu7~jh') in my upstart- job-logging PPA: https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging/ Please install and provide feedback. ** Changed in: upstart (Ubuntu Precise) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
** Also affects: upstart Importance: Undecided Status: New ** Changed in: upstart Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart Importance: Undecided => High ** Changed in: upstart Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
** Changed in: upstart (Ubuntu Precise) Assignee: (unassigned) => James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/926468/+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 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
@Jason: thanks for taking the time to look at this. Yes, I can confirm your understanding of the problem as I had come to exactly the same conclusion! :-) I have raised a bug on openssh for the stderr fd leak: https://bugzilla.mindrot.org/show_bug.cgi?id=1976 ** Bug watch added: OpenSSH Portable Bugzilla #1976 https://bugzilla.mindrot.org/show_bug.cgi?id=1976 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/926468/+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 862392] Re: unity/compiz dies horribly if kvm interrupted when iconified
** Also affects: kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/862392 Title: unity/compiz dies horribly if kvm interrupted when iconified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/862392/+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 771305] Re: smbd does not start on first boot with 20110426
Hi Jamie - your syslog shows that Upstart attempted to restart smbd a number of times, but since smbd kept exiting in error, it eventually hit the upstart respawn limit at which point Upstart stopped attempting to start it. The problem suggests an issue either with the smbd binary or one of the files it reads (maybe an invalid /etc/samba/smb.conf?) -- 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/771305 Title: smbd does not start on first boot with 20110426 -- 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 718664] Re: upstart config fo file autofs5 requires space
** Branch linked: lp:~jamesodhunt/ubuntu/natty/autofs5/fix-upstart- config -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in ubuntu. https://bugs.launchpad.net/bugs/718664 Title: upstart config fo file autofs5 requires space -- 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 718664] Re: upstart config fo file autofs5 requires space
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in ubuntu. https://bugs.launchpad.net/bugs/718664 Title: upstart config fo file autofs5 requires space -- 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 718664] [NEW] upstart config fo file autofs5 requires space
Public bug reported: Binary package hint: autofs5 /etc/init/autofs.conf contains the following stop on condition: stop on runlevel[!2345] This will stop the autofs service when the event called "runlevel[!2345]" is emitted! There is a missing space here. autofs.conf should specify: stop on runlevel [!2345] Which will stop the service when the "runlevel" event is emitted with a RUNLEVEL variable of 0,1 or 6 specified. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: autofs5 5.0.5-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10 Uname: Linux 2.6.35-25-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Feb 14 11:02:14 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: autofs5 ** Affects: autofs5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in ubuntu. https://bugs.launchpad.net/bugs/718664 Title: upstart config fo file autofs5 requires space -- 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 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Equivalent sysvinit patch for Natty. ** Patch added: "natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff" https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824656/+files/natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- 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 672177] Re: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted
Equivalent sysvinit patch for Maverick. ** Patch added: "maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.diff" https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824655/+files/maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- 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
