Public bug reported:
I've played around with steam-lxc, but the container fails to start.
Some debugging reveals:
>> sudo lxc-start -l DEBUG --name siretart-steam
lxc-start: Error creating cgroups
lxc-start: failed to spawn 'siretart-steam'
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: l
From: /var/log/lxc/siretart-steam.log
lxc-start 1367650042.758 INFO lxc_start_ui - using rcfile
/var/lib/lxc/siretart-steam/config
lxc-start 1367650042.758 INFO lxc_apparmor - aa_enabled set to 1
lxc-start 1367650042.758 DEBUGlxc_start - sigchild handler set
l
How can I debug the problem further?
--
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/1176287
Title:
lxc-start: Error creating cgroups
To manage notifications about this bug go to:
https
The error message is thrown here in the code:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/raring/lxc/raring/view/head:/src/lxc/cgroup.c#L578
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.
the lxc-start command seems to massively create cgroups:
>> find /sys/fs/cgroup/ -name 'siretart-steam*' -print | wc -l
589773
What does create that many cgroups?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:
** Attachment added: "find_sys_fs_cgroup.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1176287/+attachment/3664775/+files/find_sys_fs_cgroup.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://
** Attachment added: "dpkg_l_cgroup"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1176287/+attachment/3664777/+files/dpkg_l_cgroup
--
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/
** Attachment added: "lxc-debug.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1176287/+attachment/3664776/+files/lxc-debug.out
--
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/
** Attachment added: "proc_self_mounts"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1176287/+attachment/3664778/+files/proc_self_mounts
--
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
I've added all requested information now. Please indicate if there is
anything else that may be helpful for diagnosing the problem.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
This new version of lxc does indeed fix the symptoms for me on raring.
Thanks for the prompt update.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
h
How about adding a pre-stop script to /etc/init/libvirt-bin.conf that
uses /usr/bin/virsh to iterate over all running guests to shut them
down? Probably this should be done a) in parallel and b) supervised by
reasonable timeouts. So technically, it might make sense to implement
that pre-stop script
ignore my previous comment, I should have read the whole thread in more
detail.
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
U
instead of destroying vms, wouldn't be a more elegant solution to "save"
the state of the VM in a statefile?
On bootup, upstart would check for such statefiles and restore the
VMs. This would work even for VMs that don't react to ACPI events
properly and saves the VM's uptimes.
--
Should shut do
r copy the pid files into /lib/init/rw/sendsigs.omit.d? AFAIUI,
the upstart job should be executed before the sendsigs init script, or
is there another race here?
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
Should shut down domains on system shutdown
https://bugs.launchpad.ne
comment #28 indicates that the problem is still in maverick, reopening.
please also consider raising the importance of this bug, as it is a
serious issue for many common setups.
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Confirmed
** Also affects: libvirt (Ubuntu Lucid)
Im
this bug has nothing to do with VDE. It seems that ubuntu's current
version of libvirt/kvm-qemu does not implement boot ordering correctly.
this seems to be present in fedora as well:
https://bugzilla.redhat.com/show_bug.cgi?id=472236
** Bug watch added: Red Hat Bugzilla #472236
https://bugzil
** Also affects: qemu
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/551545
Title:
PXE netboot not booting localboot from virtio-disk
-
lucid-updates and lucid-proposed ship the same package and from the
changelog I cannot see what change would be related to this big.
I've just confirmed by testing that the bug still applies to the most
uptodate packages that are available for lucid.
** Changed in: qemu-kvm (Ubuntu)
Status
Public bug reported:
Binary package hint: qemu-kvm
steps to reproduce:
- install qemu, libvirt-bin, virt-manager, kvm-pxe
- create new virtual machine
- connect some installation medium to the virtual CD drive
- configure boot device order: Boot Options -> Boot Device Order:
- check PXE,
This issue may or may not be related to bug #551545
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/648228
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs m
On Di, Sep 28, 2010 at 00:07:32 (CEST), C de-Avillez wrote:
> Hi Reinhard,
>
> What version of the packages are you running?
current maverick from the day I've reported the issue.
> Also can you attach the XML for the VM?
will do later today.
--
Gruesse/greetings,
Reinha
sorry for the delay, here is the xml
** Attachment added: "debtest.xml"
https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/648228/+attachment/1673373/+files/debtest.xml
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
--
boot ordering broken: does not try next boo
used versions:
ii libvirt-bin 0.8.3-1ubuntu14 the programs for the
libvirt library
ii virt-manager0.8.4-7ubuntu1 desktop application for
managing virtual machines
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/6
Well, pressing 'q' indeed makes it proceed with the installation cdrom.
However, it doesn't do so non-interactively.
In my setup, I configure both VMs and physical machines to boot via PXE,
but by default have them boot locally. Only in case they require
maintenance, the PXE configuration is chang
** Bug watch added: Debian Bug tracker #567606
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567606
** Also affects: libvirt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567606
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Public bug reported:
>From /etc/network/if-up.d/ntpdate:
invoke-rc.d --quiet ntp stop >/dev/null 2>&1 || true
/usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null || :
invoke-rc.d --quiet ntp start >/dev/null 2>&1 || true
This code is supposed to stop the running ntpd. However, this fails if opennt
** Also affects: ntp (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://
This is very likely the cause for bugs such as
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330587 or
- http://www.jfix.com/news/?p=92
** Bug watch added: Debian Bug tracker #330587
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330587
--
You received this bug notification because
I have a package ready for oneiric-updates, see the linked branch. Is
this something that warrants an SRU?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/872210
Title:
/etc/network/if-u
** Changed in: ntp (Ubuntu Oneiric)
Milestone: None => oneiric-updates
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/872210
Title:
/etc/network/if-up.d/ntpdate: Fails to stop openn
nto the package.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubu
milar problems could arise with
/usr/local/ not on / but custom modifications.
However I wonder if S15wpa-ifupdown should be moved to S41wpa-ifupdown
instead. That *should* cause less breakage and do the right thing
generally.
comments?
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
-
luchio <[EMAIL PROTECTED]> writes:
> Reinhard Tartler wrote:
>> I'm unsure if that is the correct solution. It will most likely to break
>> systems that have /usr not on /. Similar problems could arise with
>> /usr/local/ not on / but custom modifications.
>
34 matches
Mail list logo
