*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
The title of this bug is 'lxc stop will hang forever' - are you still
seeing that as well?
In both this and 1073238, you claimed that 3.7 fixed it for you. You're
saying that lvremove hanging happened in 3
** Description changed:
+ ***
+ 1. Impact: lxc-clone for lvm-backed containers is broken
+ 2. Development fix: saucy fixed the use of wrong pathnames in the
+ lxc-clone script.
+ 3. Stable fix: same as development fix
+ 4. Test case:
+ * Create an lvm backed
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] Write
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: DONE
[serge-hallyn
Fix has been committed upstream for some time.
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1177604
Title:
lxc-ps
irc discussions tracked this down - the backports package has lxc-halt
from debian, rather than (as it is supposed to have) symlink to lxc-
shutdown.
Markign confirmed. Until this is fix released, please use lxc-shutdown
instead.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Triaged
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1182085
Title:
document lxc.loglevel and lxc.logfile in lxc.conf manpag
** 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/1029777
Title:
Use overlayfs in lxc-clone
To manage notifications
Still haven't actually reproduced, but marking confirmed as I believe
it's valid.
This should be fixed when 0.9.0 is backported.
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification
actually I"m not sure how i should mark this status. It's fix released
as it's not broken in saucy (or raring). i can't mark it as affecting
precise as it only affects precise-backports, but that is not a valid
target.
--
You received this bug notification because you are a member of Ubuntu
Ser
I can't reproduce this on an uptodate raring server.
You filed this against qemu-kvm, but the bug is claimed against lxc. I
will mark ti as affecting lxc - please then run 'apport-collect 1186501'
to get some helpful debugging info uploaded to the bug.
It might also help to do a 'lxc-start -n -
Blueprint changed by Serge Hallyn:
Definition Status: Discussion => Obsolete
--
KVM on arm
https://blueprints.launchpad.net/cdo-status-tracker/+spec/servercloud-s-cloud-kvm-on-arm
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
Could you show the exact remmina command you were using to connect to
the VM?
If you do 'gvncviewer localhost:0' (from the same machine on which kvm
is running), what do you see?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
Quoting f3a97 (1180...@bugs.launchpad.net):
> Hi Serge,
>
> I'm invoking remmina from the Unity shell, not from the terminal.
Could you please tell me, perhaps with some screenshots, exactly what
boxes you fill in how to start the connection?
> As regard your question: I'm connecting to the VM v
*** This bug is a duplicate of bug 1174148 ***
https://bugs.launchpad.net/bugs/1174148
@Will,
yes, please go and verify bug 1174148. The fix is uploaded to precise-
proposed.
** This bug has been marked a duplicate of bug 1174148
Can't build a raring VM
--
You received this bug notific
@Neil,
yes, please do raise a new bug.
--
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/993706
Title:
Fix lxc-execute without rootfs failing apparmor transitions
To manage notifications
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1168526
Title:
race condition causing lxc to not detect container init
Is this still happening for you?
Are you behind a proxy that would explain this behavior?
(I wonder if this could actually be a bug/misconfiguration in your ca-
certificates?)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubu
** Tags added: security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188069
Title:
apache2 mod_rewrite CVE 2013-1862
To manage notifications about this bug go to:
https://bugs.l
Thanks for reporting this bug.
Were you doing anything in particular when this happened?
** Changed in: samba (Ubuntu)
Status: New => Confirmed
** Changed in: samba (Ubuntu)
Importance: Undecided => High
** Changed in: samba (Ubuntu)
Status: Confirmed => Incomplete
--
You rec
Quoting Andreas Wirooks (nudgegoon...@hotmail.com):
> It still happenes. Wouldn't it be better to move this bug report somewhere
> else?
Probably, but as you point out I'm not sure where. I'll mark this as
affecting wget and ca-certificates.
Could you show the result of
curl -Iv https://cloud-
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1188501
Title:
lxc-execute fails to start container without rootfs
To manage
: (unassigned) => Serge Hallyn (serge-hallyn)
--
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/1188501
Title:
lxc-execute fails to start container without rootfs
To manage notification
Thanks for reporting this bug and pointing to the nice simple fix. I"ll
work on SRUing this.
Would you mind adding a detailed test case to the description? (The
symlinking part is fine, but the configuration file plus a neat way to
determine that the task failed to be reclassified.)
** Changed
@Jon,
I'm only allowed to nominate this bug for precise. Could you please
accept the nomination, and, if you have time, complete the SRU (else
shout and I'll continue with it).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup
Public bug reported:
doing
lxc-create -t ubuntu -n lucid1 -- -r lucid
lxc-start -n lucid -d
lxc-stop -n lucid
echo $?
shows that lxc-stop returns -1 even though the container ends up being
stopped. The default behavior should be to wait for the container to
cleanly shut down and return
** Patch added: "0001-lxc_stop-return-success-if-api_shutdown-succeeded.patch"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1189512/+attachment/3699923/+files/0001-lxc_stop-return-success-if-api_shutdown-succeeded.patch
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
**
(The above patch has been sent upstream)
** Changed in: lxc (Ubuntu)
Importance: High => Medium
--
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/1189512
Title:
lxc-stop returns failur
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1189512
Title:
lxc-stop returns failure on success
To manage notifica
THis is being addressed (by Dwight) upstream. The fix will be in saucy
before release.
--
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/987770
Title:
lxc-start: wrong terminal size
To m
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an
The go API bindings have been tested with a large number of simultaneous
create/start/destroys, so I believe the upstream API thread-safety work
must have fixed this at least upstream.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification bec
** Changed in: qemu-kvm (Ubuntu Precise)
Status: New => Triaged
** Changed in: qemu-kvm (Ubuntu Quantal)
Importance: Undecided => High
--
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
** Changed in: libcgroup (Ubuntu Precise)
Status: New => In Progress
** Changed in: libcgroup (Ubuntu Precise)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: libcgroup (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug not
Thanks, ojab - tried out your testcase, worked like a charm. (For
manual reproduction, I'd recommend sleeping 20 rather than 2)
** Description changed:
Oh hai!
I've found that 0.37.1-1ubuntu10 in precise/LTS cannot process symlinked
executables correctly, the testcase is
>$ python -c "
Confirmed in raring.
** 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/1180777
Title:
Windows 7 VM freeze on Ubuntu 1
Actually no, in my case after I had started up IE and left it sitting,
the desktop logged me out, which made windows change its network
settings so that RDP was not allowed. I had to log back in over spicy
before I could reconnect over RDP.
--
You received this bug notification because you are a
In fact that did not suffice (this is raring, not precise) - windows
needed to reboot to reset the model=rtl8139 nic (over tap device).
Could you tell me which network device type you are using?
It looks like I should set up a precise host on which to test.
--
You received this bug notification
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1188820
Title:
shadow file permissions broken
To manage no
** Changed in: spamassassin (Ubuntu)
Importance: Undecided => Medium
** Changed in: spamassassin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad
** Changed in: maas (Ubuntu)
Status: New => Triaged
** Changed in: maas (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1185261
Title:
M
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
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/b
** Changed in: maas (Ubuntu)
Importance: Undecided => High
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1185160
Title:
** Changed in: euca2ools (Ubuntu)
Importance: Undecided => Low
** Changed in: euca2ools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in Ubuntu.
https://bugs.launchpad.net/bugs/11
** No longer affects: php5 (Ubuntu)
** Changed in: libjpeg-turbo (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1189939
Title:
Initialization
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: DONE
[serge-hallyn
Hi Chris,
Do you mind if the patch comment gets updated to something like:
While searching for available clusters, if we detect an ongoing AIO
write request, then we restart after the other has completed. By not
re-setting i to 0, we fail to re-check clusters which may no longer be
available.
-
> I noticed when running ps auxf on the host machine, that various processes
> were ascribed to the wrong users -- and surmised that it was just a result of
> what the host thought which names belonged to those userid's; but I hoped it
> wouldn't let me kill them as that user.
>
> So I su'd to
signee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: libvirt (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
+ =
+ SRU Justification
+ 1. Impact: cannot attach host usb device to domain 2 after attaching it to
domain 1
Fix verified on 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/1113821
Title:
libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade
To manage notifications about this bug
Also verified on quantal.
** 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.
https://bugs.launchpad.net/bugs/1113821
Title:
libvirt-bin deletes /etc/d
k.
Thanks for pointing this out!
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: Fix Released => Triaged
** Changed in: qemu-kvm (Ubuntu Precise)
Status: Fix Released => Triaged
** Changed in: qemu-kvm (Ubuntu Precise)
Assignee: (unassigned) => Serge Hallyn (serge-
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: DONE
[serge-hallyn
Quoting Pavel Bennett (launch...@pavelbennett.com):
> Hey Serge, were you able to get a reliable repro for this? I have a
No, I wasn't (assuming you mean with our workaround in place in the
ubuntu package).
In comment #8 you said node.js was able to reproduce this. Regarding
that,
1. Does that
Quoting Pavel Bennett (launch...@pavelbennett.com):
> I can't try Saucy right now, but the repro instructions with kernel
> versions are in the original post and in #2.
>
> We've tried node v0.11.2 as well on Raring and got the repro.
>
> Repro summary:
>
> Install any of the above kernels, such
Quoting Pavel Bennett (launch...@pavelbennett.com):
> Sure, run these inside the container:
>
> git clone https://github.com/joyent/node.git --depth 1
>
> cd node
> ./configure
> make -j9
> sudo make install
>
> Then the binary will be at /usr/local/bin/node
>
> It's v0.11.3-pre, but should sti
Thanks for reporting this bug. Could you please show the results of ps
-ef and sudo lsof ?
I gather /var/lib/lxc is a btrfs filesystem? The hang happens before it
debootstraps, right? Could you also show the ps -ef while lxc-create is
hanging?
** Changed in: lxc (Ubuntu)
Importance: Undecid
(Tried to reproduce this in a nested raring container with a btrfs
loopback fs mounted under /var/lib/lxc)
--
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/1193594
Title:
lxc-create hangi
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1193594
Title:
lxc-create hanging
To manage notifications about this bug go
** Also affects: vm-builder (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: vm-builder (Ubuntu)
Status: Fix Released => Fix Committed
** Also affects: vm-builder (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: vm-builder (Ubuntu Rari
Thanks for the patch. My guess would be it was applied in the package
source, but not in the bzr tree, so after the next bzr tree update the
fix was lost. But I'm not sure.
Patch pushed to bzr and to the saucy tree. There are vmbuilder packages
awaiting verification in all the prior releases ex
*** This bug is a duplicate of bug 1182540 ***
https://bugs.launchpad.net/bugs/1182540
Hi,
so I don't know how to explain this, but udevd is holding
/run/lock/subsys/lxc-ubuntu. That file is used by the ubuntu lxc
template to mutex the ubuntu template cache entries under
/var/cache/lxc.
ude
*** This bug is a duplicate of bug 1182540 ***
https://bugs.launchpad.net/bugs/1182540
Thanks to cjwatson for remembering the actual bug (bug 1182540). WIll
mark this a duplicate of that.
** This bug has been marked a duplicate of bug 1182540
Daemon-suppression code in installer breaks ne
*** This bug is a duplicate of bug 1182540 ***
https://bugs.launchpad.net/bugs/1182540
Quoting Robert Collins (1193...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1182540 ***
> https://bugs.launchpad.net/bugs/1182540
>
> Indeed, that worked - thanks. Will everyone upgrading
Hi,
(You probably knkow this, but to explain my request, the RDP connection
goes over the VM's virtual network card to talk directly to the VM.
Provided you have only a single VM running, 'gvncviewer localhost:0' (or
the equivalent with ssh port forwarding if you can't run X on the host)
talks to
Unfortunately I don't have any hardware to reproduce this with.
Could you please:
1. Attach /var/log/libvirt/qemu/w.log
2. Try running this vm with kvm by hand as per
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM ?
(i.e. the kvm command in step 6, something like "kvm
Setting verification-failed to indicate we'd like 1.0+noroms-0ubuntu14.9
dropped. 1.0+noroms-0ubuntu14.10 is in Unapproved, and has the better
fix.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Se
** Also affects: lxc (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu Raring)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu Raring)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Serv
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - write
Quoting Pavel Bennett (1196...@bugs.launchpad.net):
> If it matters, I SIGKILL my lxc-start processes instead of using lxc-
> stop. Could that have any negative implications?
Yes, the lxc-start process itself is not the container init, so killing
it will prevent lxc from doing cleanup. Please try
> I am sorry.
>
> Host Kernel : 3.10.0-rc5+ [upstream kernel fedora base], both the source
> and destination host are the same.
>
> We test the upstream kernel, qemu and libvirt. We don't have ubuntu.
Oh, I see - then please see http://libvirt.org/bugs.html (specifically
"General libvirt bug rep
** Description changed:
+
+ Impact: cannot lxc-execute in a container without private rootfs
+ Development fix: mount /proc when no rootfs is specified
+ Stable fix: same as development fix
+ Test case:
+ sudo lxc-execute --name test /bin/bash
+ Without the fix
(Marking medium priority as there is a workaround and it is not the
archive package - not low, since your first run-in with this bug will
shut down your host)
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
S
Thanks for the info
affects: linux
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196295
Title:
lxc-start enters
Ok - thanks - I was able to reproduce this in a raring VM with 4 cores.
I thought this might be a tiny race window between us blocking signals
and creating the signalfd, so I reversed those (a patch which I may yet
send upstream) - but that didn't solve the issue.
--
You received this bug notifi
It does seem like this must be a kernel bug in epoll+signalfd (or a hard
to spot misuse thereof in lxc).
When I instrument the signal_handler which is executed when epoll_wait
returns a signalfd event, I do get a sigchld for the very first task
which is spawned (a test to see if kernel supports pi
Fix is upstream.
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/987770
Title:
lxc-start: wrong terminal size
To m
Thanks for reporting this bug.
assignee: utlemming
status: confirmed
importance: low
** Changed in: lxc (Ubuntu)
Importance: Undecided => Low
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming)
--
Thanks for reporting this bug.
assignee: utlemming
status: confirmed
importance: medium
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming
Marking invalid as I couldn't reproduce, and IIUC you will re-try with
fresh containers.
If you run into this again, please re-mark it new and do a 'apport-
collect 1196518'.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member
ed by using the waitpid loop as below.
>From 7333b77759794f5420ea6898494073a28cac445f Mon Sep 17 00:00:00 2001
From: Serge Hallyn
Date: Wed, 3 Jul 2013 14:13:08 -0500
Subject: [PATCH 1/1] start.c:signal_handler: fix wrong assumption about
sigchld
The monitor process adds a signalfd to the se
** This bug is no longer a duplicate of bug 1033727
USB passthrough doesn't work anymore with qemu-kvm 1.1.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/685096
Title:
USB Pas
Quoting Robie Basak (1197...@bugs.launchpad.net):
> Public bug reported:
>
> A script cannot call lxc-start-ephemeral and get a named container in a
> reliable, race-free way.
>
> Having the caller specify a name directly is racy, since the name could
> have been taken in between checking that it
summary: lxc-start-ephemeral - provide terse -d output option
status: Triaged
importance: medium
--
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/1197754
Title:
"lxc-start-ephemeral -d"
** Changed in: lxc (Ubuntu)
Status: Incomplete => 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/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - writ
I'll post a patch to be less stringent about that check.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Ah, wait - the simpler solution would be for the mountcgroup hook to set
the device cgroup accesses (per the container config) before creating
${container}.real.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bug
** No longer affects: linux (Ubuntu)
--
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/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - write
/sys/fs/cgroup/devices/l
I'm testing this patch to solve the issue. So far it works on my
simplest case. I will run the lxc testsuite to check for some
regressions.
** Attachment added: "0011-cgroup-hook-handle-stricter-kernel"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3726408/+files/001
** 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.
Thanks for submitting this bug. (Please do try to open separate bugs
for each issue) The second part of it (sshd) has been fixed upstream
just today (with a patch sent a few days ago). Please open a new bug
for that one, and I'll SRU it to raring as I assume that's where you
want the fix.
The f
Ok, for the record I cannot reproduce this no precise - I've tried with
both an 8 core fast precise host, and a 4 core precise kvm guest - but
using the same lxc version from the daily ubuntu-lxc ppa.
So it appears to be a kernel regression between 3.2 and 3.8.
--
You received this bug notificat
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: DONE
[serge-hallyn
This bug is introduced between v3.7 and v3.8, by commit:
af4b8a83add95ef40716401395b44a1b579965f4 pidns: Wait in
zap_pid_ns_processes until pid_ns->nr_hashed == 1
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bot-stop-nagging
--
You received this bu
Would you be able to test this with upstream qemu?
git clone git://git.qemu.org/qemu.git
cd qemu
./configure --target-list=x86_64-softmmu
make -j4
cd x86_64-softmmu
./qemu-system-x86_64 -enable-kvm -m 512 -device pci-assign,host=03:00.1 -boot d
If that works, then we just need to look for the com
I can't tell when this was assigned to me, but it's not clear to me
based on stgraber.vs.rbasak which is the right course to follow.
Is high priority right here? There is an obvious workaround iiuc, and
it affects very few people.
** Changed in: lxc (Ubuntu)
Assignee: Serge Hal
> When lxc-create fails (eg. due to bug 1166841), then it leaves
> /run/lock/subsys/lxc-ubuntu lying around. A subsequent attempt to run
The file sticks around but no task has it locked, so lxc-create can
continue.
Can you please
a) show the output of lsof /run/lock/subsys/lxc-ubuntu
Quoting Robie Basak (1200...@bugs.launchpad.net):
> $ sudo lsof /var/lock/subsys/lxc-ubuntu
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> udevd 6564 root 200w REG 0,170 598420
> /run/lock/subsys/lxc-ubuntu
Ah, I believe this is *yet another* dup of bug 1182540.
Pl
Pushed proposed packages for precise and quantal.
** Changed in: qemu-kvm (Ubuntu Precise)
Status: Triaged => In Progress
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
Thanks! So it sounds like the problem is actually in ipxe.
Saucy has a new ipxe (from 9 days ago). However simply installing it
alongside precise's qemu-kvm probably won't work.
(I do see a few commits in the git tree which could perhaps fix this)
Is it possible for you to test this with saucy,
401 - 500 of 1266 matches
Mail list logo
