** Changed in: lxc (Ubuntu)
Status: Invalid = Triaged
** Summary changed:
- lxc-create fails if LANG != en_GB.UTF-8
+ lxc-create fails if LANG is not valid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Marking invalid against libvirt, since libvirt is simply responding to
requests from virt-manager.
** Changed in: libvirt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Note, this bug is in
http://ubuntu-
cloud.archive.canonical.com/ubuntu/pool/main/n/nova/nova_2013.1-0ubuntu1~cloud0.dsc
but does not exist in precise-updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Thanks. Given that info, I will mark this invalid - not meaning you
didnt' have a problem, but meaning we can't reproduce.
If you have further problems, please do open a bug against update-
manager.
** Changed in: samba (Ubuntu)
Status: Incomplete = Invalid
** Changed in: debconf
Marking invalid as the reproducer has been fixed.
** Changed in: bacula (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1156240
Title:
Quoting Seth Arnold (509...@bugs.launchpad.net):
Urgh. sorry for losing track of this bug. I forgot to subscribe after
submitting my comment.
I believe your proposed additional check would be sufficient. I _think_
better might be to destroy the lock pointer in the shared structure when
Oh but I'm being silly - once the use count goes to 0 it
cannot go back up, so we can check for that before trying
to take the lock.
--
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/509647
Quoting Pavel Bennett (launch...@pavelbennett.com):
Public bug reported:
For the purpose of the repro, my lxc init process is node.js v0.11.0
(built from source) with a single line:
process.exit(0);
Thanks. This is a race condition we've seen before in lxc-execute.
Precisely which
Can you give us the URL?
--
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/1047040
Title:
kvm crashed on precise - memory corruption
To manage notifications about this bug go to:
** Changed in: libvirt (Ubuntu Quantal)
Status: Triaged = In Progress
--
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/1157332
Title:
/etc/dnsmasq.d-available/lxc circular link
** 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/1100843
Title:
Live Migration Causes Performance Issues
To manage
Quoting Pavel Bennett (launch...@pavelbennett.com):
Btw, that queueing mode would simply mean not calling epoll_wait until
the pid is available. This shouldn't require managing a queue ourselves.
Can you think of anything that this would break?
No - I had wanted to do this originally, but
It's too late for a large FFE. We've fixed bug 1157626 with a
cherrypick to 1.0.2. Luckily this means we have 1.0.4 ready and
packaged for when s opens :)
** Changed in: libvirt (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
2013-04-05 10:20:11,231: twisted@ERROR: Fatal Python error: Py_Initialize:
Unable to get the locale encoding
2013-04-05 10:20:11,232: twisted@ERROR: File
/usr/lib/python2.7/encodings/__init__.py, line 123
2013-04-05 10:20:11,232: twisted@ERROR: raise CodecRegistryError,\
2013-04-05
The newest kernel I've tests on is 3.8.0-17-generic. I'll need to set
up a system with the daily upstream build and re-test.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received
*** This bug is a duplicate of bug 1157212 ***
https://bugs.launchpad.net/bugs/1157212
** This bug has been marked a duplicate of bug 1157212
just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP
SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel
*** This bug is a duplicate of bug 1157212 ***
https://bugs.launchpad.net/bugs/1157212
** This bug has been marked a duplicate of bug 1157212
just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP
SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel
*** This bug is a duplicate of bug 1164843 ***
https://bugs.launchpad.net/bugs/1164843
** This bug has been marked a duplicate of bug 1164843
juju agent fails to start machine by using lxc as provider
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I'm marking this confirmed based on duplicate bug.
** Changed in: juju (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1164843
Title:
juju
when you tested the newer kernel you weren't using a different
(unpatched) lxc?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification because you are a member
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
Note lxc-start-ephemeral should soon be a wrapper around the
python api bindings of the api clone command, which will mean
that lvm snapshotted ephemeral containers will come free.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Thanks for taking the time to report this bug. However, in order to
use lxc-execute, you must install lxc-init in the container, by
chrooting into or lxc-starting the container, and doign
apt-get install --no-install-recommends lxc
After that, lxc-execute with a noninteractive command
Thanks for reporting this bug. Unfortunately it's more complicated
than this and I'm not sure waht you want is possible. It would be
if everything were simple system containers, however you can also
lxc-start and lxc-execute things with / as rootfs and custom
config files - meaning there is no
Hi,
is your environment such that you'd be able to build and run qemu from
git so as to (a) test that it is fixed upstream, and if so (b) bisect to
determine the fix?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member
-24 15:50:20.0 +
@@ -1,3 +1,9 @@
+libvirt (0.9.8-2ubuntu17.10) precise-proposed; urgency=low
+
+ * debian/libvirt-bin.{dirs,install}: install dnsmasq.d-available/libvirt-bin
+
+ -- Serge Hallyn serge.hal...@ubuntu.com Wed, 24 Apr 2013 15:49:38 +
+
libvirt (0.9.8-2ubuntu17.9
The fix for libvirt is bad in both raring and precise (and in unapproved
quantal), because the /etc/dnsmasq.d-available was being copied to
debian/tmp but not in libvirt-bin.{dirs,install}.
Verification failed.
** Changed in: libvirt (Ubuntu Raring)
Status: Fix Released = In Progress
**
Thanks for submitting this bug. Could you please attach your
/etc/postfix/main.cf file (with any passwords and ip address removed) to
this bug?
** Changed in: postfix (Ubuntu)
Importance: Undecided = Medium
** Changed in: postfix (Ubuntu)
Status: New = Incomplete
--
You received
Fix committed in upstream git.
** Changed in: lxc (Ubuntu)
Status: In Progress = Fix Committed
--
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/1135871
Title:
arm containers
I believe this is fixed in upstream git.
** Changed in: lxc (Ubuntu)
Status: New = Fix Committed
--
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/1124526
Title:
potential race in
Fix committed in upstream git.
** Changed in: lxc (Ubuntu)
Status: In Progress = Fix Committed
--
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/1081786
Title:
lxc-create doesn't
Thanks for the info. I was hoping you could test with
git://git.qemu.org/qemu.git so we could know if this is fixed in the
upstream development tree.
Separately, the next time it is hung, could you show the results of
ifconfig -a
brctl show
arp -n
netstat -nr
** Changed in: qemu-kvm
uploaded libvirt fix to precise through saucy.
--
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/1113821
Title:
libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade
To manage
** Changed in: qemu-kvm (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/1172091
Title:
KVM guests with bridged network drops out
Waiting on a microsoft license, hoping to be able to test this in the
next 2 weeks.
--
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/685096
Title:
USB Passthrough not working for
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = High
** Changed in: vm-builder (Ubuntu)
Status: New = In Progress
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Also affects: vm-builder (Ubuntu Raring)
Importance
** Also affects: vm-builder (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: vm-builder (Ubuntu Quantal)
Importance: Undecided = High
** Changed in: vm-builder (Ubuntu Quantal)
Status: New = Triaged
--
You received this bug notification because you are a
Hi,
as I'm setting up to reproduce this, I'm wondering exactly what to do
with eth1. You are putting into br1, and leaving both eth1 and br1
unconfigured, at least according to interfaces(5). Are you later on
manually configuring it? Then your vms get their nics also bridged to
br1, so how
@Adam,
The raring-proposed version of libvirt-bin properly sets up
/etc/dnsmasq.d/libvirt-bin, and remove/install does not cause the file
to be dropped. (fix verified)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
*** This bug is a duplicate of bug 1124384 ***
https://bugs.launchpad.net/bugs/1124384
** This bug has been marked a duplicate of bug 1124384
Configuration reload clears event that others jobs may be waiting on
--
You received this bug notification because you are a member of Ubuntu
Thanks for submitting this bug. Based on dmesg, it looks like the
vsftpd executable was deleted before the attempt to remove the package.
If I understand correctly, you have now successfully removed vsftpd, and
dont' care to reinstall it. I'll go ahed and mark the bug invalid
(meaning
Quoting Dyson Simmons (dysonsimm...@gmail.com):
Hi Serge,
eth0 and eth1 both plug into a Cisco switch. They are on separate vlans.
eth0 is an internal ip range (10.10.x.x) and eth1 is used for a pool of
public IP addresses we have (203.0.141.x).
I don't want the VM host to have a public
Coudl you please show the result of
find /sys/fs/cgroup -maxdepth 3
Also, please post the full debug.out file after doing
sudo lxc-start -l info -o debug.out --name siretart-steam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Sorry, please also show the output of:
dpkg -l | grep cgroup
cat /proc/self/mounts
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
lxc-ps looks at /sys/fs/cgroup/cpuset/lxc/$container/tasks to get a list
of tasks in the container. However, in the face of either failed
previous container startups, or multiple containers with theh same name
in differnet lxcpaths, the container's cgroup could be
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team
A proposed fix has been sent to the mailing list. I'm not sure whether
we'll go with that patch, or re-write lxc-ps.
** Changed in: lxc (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Patch added: proposed fix.
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177604/+attachment/3669323/+files/0001-lxc-ps-handle-cgroup-collisions.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thanks for reporting this bug.
I can't reproduce anything with lxc-destroy. lxc-destroy on a running
container gives me
ubuntu@server-6896fdb5-46e0-47f9-b547-0a841dbf4c75:~$ sudo lxc-destroy -n r1
lxc-destroy: 'r1' state: RUNNING; aborted
lxc-info tries to talk to the container-specific
Could you tell me where to find the plan9port package you isntalled in
the container?
--
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/1177583
Title:
lxc-list crash after lxc-destory of
To be clear - the per-container 'command' handler, which is a part of
the lxc-start process, cannot multiplex, so if one command were to be,
say, suspended while having an open connection to the handler, or if
lxc-start itself were to be hung, that could cause lxc-info to hang (as
it was doing for
Unfortunately I still can't reproduce this.
Could you try re-tracing your steps to see if you can reproduce?
You're on (uptodate) raring right?
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Summary changed:
- lxc-list crash after lxc-destory of a running container
+ lxc-list
Could you please try
sudo apt-get install python3-dbg lxc-dbg apport-retrace
sudo apport-retrace -g _usr_bin_lxc-ls.0.crash
(type 'where', show the output)
Or, if that doesn't seem to work,
mkdir yyy
apport-unpack _usr_bin_lxc-ls.0.crash yyy
cd yyy
gdb python3 CoreDump
where
--
You received
** 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 qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1100843
Title:
Live Migration Causes Performance Issues
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1178721
Title:
multipathd fails to create mappings
** Package changed: kvm (Ubuntu) = qemu (Ubuntu)
--
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/1178884
Title:
unhelpful kvm error msg thrown when cache=none and no direct IO
To
Is someone working on, or planning to work on, a bisect to find out
which commit fixed it in v3.9-rc4?
--
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/1157589
Title:
kvm hangs for
-
test/sys/fs/cgroup.
I'll work on a fix for lxc.
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Importance: High = Critical
** Changed in: lxc (Ubuntu)
Status: Confirmed = In Progress
** Also affects: lxc (Ubuntu Raring
** Description changed:
- I've played around with steam-lxc, but the container fails to start.
- Some debugging reveals:
+ === SRU Justification ===
+ 1. Impact: users who have cgroups mounted in more than one place will hang
thier
+ system when starting an lxc container
+ 2.
Blueprint changed by Serge Hallyn:
Whiteboard changed:
This blueprint is broken into 3 sections - libcgroup, lxc, and
qemu+libvirt.
Background on libcgroup
libcgroup is a package which provides:
-a. Flexible boot-time setup of cgroups
-b. Command line tools
Thanks for reporting this bug. Could you please give us more
information on the VM host and the client? What do you mean
by 'kvm over virtualbox'? How exactly did you set it up?
Is the remote desktop running on a windows machine?
My guess is that the answer lies in 'kvm on virtualbox', and
how
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
- [stgraber] Look into shipping logind with cgroup support by defaut: TODO
+ [stgraber] Look into shipping logind with cgroup support by defaut: POSTPONED
[serge-hallyn] put utah testcases in upstream tests/ubuntu: POSTPONED
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[serge-hallyn] (or slangasek) fix persistence issues in ed2k: POSTPONED
[serge-hallyn] (or slangasek) find a solution for useful default in ovmf for
secureboot: POSTPONED
[serge-hallyn] get openbios-ppc into archive (work
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
- [louis-bouchard] document use of cloud images in kvm in the server guide:
INPROGRESS
- [motu] package oz (see links above): TODO
- [utlemming] update https://help.ubuntu.com/community/UEC/Images for
cloud-localds: TODO
Blueprint changed by Serge Hallyn:
Assignee: Serge Hallyn = (none)
--
VMBuilder plans during R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-vmbuilder
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https
Blueprint changed by Serge Hallyn:
Whiteboard changed:
User Stories:
Karl runs some containers on his host. He doesn't want the sound card volume
being reset every time a container starts.
Joy wants 30 containers to each have access to one loop device, without any
risk of them
Blueprint changed by Serge Hallyn:
Whiteboard changed:
User Stories:
Karl runs some containers on his host. He doesn't want the sound card volume
being reset every time a container starts.
Joy wants 30 containers to each have access to one loop device, without any
risk of them
Thanks Daviey. confirmed, with quantal-proposed I get
crw-rw 1 root kvm 10, 232 May 17 15:43 /dev/kvm
** Description changed:
When qemu-system gets installed, the newly installed udev rule causes
/dev/kvm to gets chgrpd to kvm and its mode to get set to g+rw.
However, because
The bug submitter mentioned libvirt/lxc. I don't believe it has any of
the protections which lxc has against this.
** Package changed: lxc (Ubuntu) = libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Status: Invalid = New
Thanks for reporting this bug.
In order to help me reproduce it, could you please tell us in detail how
you are attaching the NIC, and what OS/release is running inside the
guest?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = High
** Changed in: qemu-kvm (Ubuntu)
Status:
Thanks for reporting this bug.
If you do
c.set_config_item(lxc.log.loglevel', '1')
before starting the container, does that help?
Also, if you cause an actual error during startup (i.e. specify a wrong
rootfs location in the configuration), does an error then at least show
up in the logfile?
Public bug reported:
lxc.conf(5) manpage needs to document lxc.loglevel and lxc.logfile.
Also check for any other missing lines (by crossreferencing
src/lxc/confile.c).
** Affects: lxc (Ubuntu)
Importance: Low
Status: Triaged
** Changed in: lxc (Ubuntu)
Status: New =
Public bug reported:
Currently we wget the ubuntu-cloud template without any integrity
verification. We then proceed to execute binaries like /bin/passwd
while still in the ubuntu-cloud template (in a chroot, but without any
effective containment). We should be verifying that the image we
@shedoh,
Please post the full xml for a failing vm.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1031063
Title:
internal error no supported architecture for os type 'hvm'
To
Thanks for reporting this bug. Unfortunately I can't quite tell from
the logs what was going on.
Could you tell us exactly what triggered this? Did this happen on 'sudo
apt-get purge qemu'? (that is the last action logged in
DpkgHistoryLog.txt)
What does 'dpkg -l | grep qemu' show now?
Could
Thanks, this is likely related to how the python bindings are
interpreting the second command. I woudl actually expect
c.set_config_item('lxc.loglevel', 'info') to work, but that
fails here too.
status: confirmed
assignee: stgraber
priority: medium
--
You received this bug notification
*** This bug is a duplicate of bug 1182085 ***
https://bugs.launchpad.net/bugs/1182085
Please add
lxc.loglevel = 1
I'm going to mark this as a dup of the bug about lxc.loglevel not being
documented in lxc.conf(5). If this does not work for you, then please
show the output and un-mark this
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
Quoting Didier Roche (didro...@ubuntu.com):
Public bug reported:
No log at all are written, even with:
lxc.loglevel = debug
lxc.logfile = /tmp/foo
When I add
lxc.loglevel=1
lxc.logfile=/tmp/foo
to
Blueprint changed by Serge Hallyn:
Definition Status: Discussion = Drafting
--
Virtualization Stack Work for Saucy
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-virtstack
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
When I took a close look the first time, it appeared to be hung in the
lxc-ubuntu template on flock.
If this is reproducible, and hangs again on flock, then it sounds like a
kernel bug and we should mark as affecting linux.
I couldn't reproduce this on a saucy canonistack instance, but that may
Marking incomplete until it is reproduced. If it happens again, then
please mark it confirmed.
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
Do you mean c-start(c) in python bindings, with
lxc.loglevel = debug
lxc.logfile = /tmp/foo
in container config, fails? If so that's very interesting. If not,
then it matches my current expectation.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- The saucy smoke test for lxc test_lxc_apparmor appears to be hung with
- saucy installations of 20130521.
+ The root of the problem as pertains to lxc is that debootstrap is
+ resulting in a udev
Thanks for submitting this bug. Note that snapshots do seem to work
(sudo lxc-clone -s -o r1 -n r2), but non-snapshot ones do indeed hang.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
** Also affects: lxc (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Saucy)
Importance: Medium
Status: Confirmed
** Changed in: lxc (Ubuntu Saucy)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification
The patch introduced to fix this in saucy should be cleanly applicable
to raring.
** Changed in: lxc (Ubuntu Raring)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Saucy)
Importance: Medium = High
** Changed in: lxc (Ubuntu Raring)
Status: New = Triaged
** Changed in: lxc
Public bug reported:
On a saucy system, after doing
sudo apt-get install lxc
/etc/default/lxc-net is correctly setup, but lxcbr0 does not exist. A
subsequent reboot or simply 'start lxc-net' manages to start it.
** Affects: lxc (Ubuntu)
Importance: High
Status: Triaged
**
Sorry, I'm not 100% clear on the context.
What exactly is 13.10? Are you trying to debootstrap a 13.10 image on a
12.04 host? Or am I misunderstanding?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Also please give the full, precise qemu-debootstrap command used.
Thanks!
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = High
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Blueprint changed by Serge Hallyn:
Whiteboard changed:
- This blueprint is broken into 3 sections - libcgroup, lxc, and
- qemu+libvirt.
+ [USER STORIES]
- Background on libcgroup
- libcgroup is a package which provides:
- a. Flexible boot-time setup of cgroups
- b. Command line
Blueprint changed by Serge Hallyn:
Work items set to:
Work items:
[serge-hallyn] (ebiederman) Push fix for XFS and user namespaces: TODO
[serge-hallyn] Fix lxc-net to be nestable with no user interaction: DONE
[serge-hallyn] Write sysctl to disable unprivileged CLONE_NEWUSER: TODO
[serge-hallyn
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
- [serge-hallyn] (ebiederman) Push fix for XFS and user namespaces: TODO
+ [ebiederm] Push fix for XFS and user namespaces: TODO
[serge-hallyn] Fix lxc-net to be nestable with no user interaction: DONE
[serge-hallyn] Write
Blueprint changed by Serge Hallyn:
Definition Status: Drafting = Review
--
Virtualization Stack Work for Saucy
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-virtstack
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
*** This bug is a duplicate of bug 1182085 ***
https://bugs.launchpad.net/bugs/1182085
Sorry, comment #2 seems to contradict the description. In the
description you say neither stdout nor stderr go to the file. In
comment #2 at the end you say stderr is not going to the file.
lxc is using
Thanks for submitting this bug.
lxc-halt is not a command installed by the lxc package. Do you know
where you got the version of lxc you are running? Please show the
result of:
which lxc-halt
dpkg -S `which lxc-halt`
and append /etc/apt/sources.list and any /etc/apt/sources.list.d/* files
you
I can't reproduce this with the stock lxc shipped with precise. Please
tell us where this version of lxc came from.
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[ebiederm] Push fix for XFS and user namespaces: TODO
[serge-hallyn] Fix lxc-net to be nestable with no user interaction: DONE
[serge-hallyn] Write sysctl to disable unprivileged CLONE_NEWUSER: TODO
[serge-hallyn
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[ebiederm] Push fix for XFS and user namespaces: TODO
[serge-hallyn] Fix lxc-net to be nestable with no user interaction: DONE
[serge-hallyn] Write sysctl to disable unprivileged CLONE_NEWUSER: TODO
[serge-hallyn
301 - 400 of 6024 matches
Mail list logo
