A few comments here.
First, some of upstream qemu's position is that nested KVM is not for
enterprise installs in the first place. (Others feel that if there are
bugs, they should be worked out)
Second, the bug appears to be a soft luckup. It seems to me the bug
should be about that. If
Moving to qemu; qemu-kvm is the source package only up to precise.
** Package changed: qemu-kvm (Ubuntu) = qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
Right so the bug her eis that your session-c2.scope was created without
giving you ownership of the directory and the tasks and cgroup.procs
files. Manually changing those permissions fixes it for me.
So this may actually be a regression in systemd itself.
--
You received this bug notification
Hi James,
to verify that this is a dup of bug 1413927, could you please
1. update your host to get lxcfs 0.4 :)
2. cat /proc/self/cgroup, get your name=systemd cgroup
3. under /sys/fs/cgroup/systemd/$(yourcgroup) chown your cgroup (i.e.
/user.slice/user-1000.slice/session-c2.scope) and the
** Package changed: lxc (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Summary changed:
- lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid
requestUser
*** This bug is a duplicate of bug 1413927 ***
https://bugs.launchpad.net/bugs/1413927
** This bug has been marked a duplicate of bug 1413927
user lxc containers fail to start under systemd: login name=systemd cgroup
is not owned by user
--
You received this bug notification because you
Sorry, I don't quite understand your questions. What do you mean by
running under the root? What is the problem at this point? If
you're getting an error creating unprivileged containers (which are
created/started without becoming the root user), see Basic unprivileged
usage at
So did we come up with a good way to detect not being on bare metal?
In fact ksm gets enabled by /etc/init/qemu-kvm which is only installed
on a subset of architectures so using virt-what may be a possibliity,
however I'd still prefer not to add virt-what as a dependency if we can
come up with a
It looks like it is mainly disabled because it is in Debian, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758189
The reasons for disabling it in Debian don't strictly apply in
ubuntu, so it may be ok for us to enable it.
status: triaged
importance: high
** Bug watch added: Debian
Great, thanks for the update. I frankly don't know what causes these cases.
They seem to happen with random
packages. i also don't know what to mark the bug, as I'm quite certain it
wasn't in cgmanager and was worked
around rather than fixed - but i'll mark it fix released.
Please reply if
Confused why this was marked confirmed/high prio, since there is as far
as I ca ntell no bug in lxc here.
The container rootfs came from an iso, but it's the configuration which
was bad. Wherever you got your configuration, fix it there to make sure
to mount a sysfs before attempting to mount
** Changed in: lxc (Ubuntu)
Importance: Undecided = Wishlist
** 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/1389864
Title:
thanks for submitting this bug. Could you tell us how you created the
container?
You should be able to solve this by adding
lxc.mount.auto = sys
as the first line of your configuration file. Please let us know if
that does not fix the container start.
** Changed in: lxc (Ubuntu)
Thanks for reporting this bug. Lucid is apparently no longer available
through the download template, so i'm going to mark this invalid as it
cannot be reproduced.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
ping
** Changed in: numactl (Ubuntu)
Importance: Undecided = High
** Changed in: numactl (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
Thanks for the update. So I'm still really curious how that defaults
file got so confused in the first place... It also may have something
to do with why you're still having trouble..
If dnsmasq is still badly installed then that would explain your
remaining issue.
What does:
sudo netstat -nr
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
Does it also fail with the qemu from
https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream ?
(This isn't quite git head, but it is qemu v2.2)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Went ahead and tested - it is in fact fixed in the v2.2 version.
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Stefan, did you ever reach any conclusions about this?
** Also affects: virtinst (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virtinst (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
** Changed in: libvirt (Ubuntu)
Importance: Undecided
Thanks very much for the update
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1001798
Title:
Remote TLS
Thanks for the update.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1319773
Title:
virt-manager unable
** Changed in: libvirt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1265425
Title:
Doesn't support arm64
To manage
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
** Changed in: qemu (Ubuntu)
Status: Triaged = Fix Released
** Changed in: libvirt (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: qemu (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
It looks as though the relevant commits were re-committed to upstream
git HEAD (9a48bcd1b82494671c09b0eefdb882581499 and
317b0a6d8ba44e9bf8f9c3dbd776c4536843d82c). So this may be fixed in
vivid, and we might be able to cherrypick the final patches to trusty.
** Package changed: libvirt
@Paul,
could you confirm whether qemu 1:2.2+dfsg-3exp~ubuntu1 from
https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream
fixes this issue? If it does then I'll go ahead and backport the patch.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1318451
Title:
100% CPU libvirtd when virt-manager is open
To
Indeed this is simply not built into the kernels (at least up to and
including Utopic)
** Package changed: libvirt (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Summary changed:
- LXC
If you'd like to file a bug against virt-manager that might be
appropriate, but libvirt absolutely should not stay running.
You can connect over vnc/spice and those connections do not go away just
bc libvirt stops. So virt-manager should be able to show that it can't
show machine details (bc
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1274972
Title:
Multiple concurrent connections cause libvirtd
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu Precise)
Status: New = Confirmed
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix
*** This bug is a duplicate of bug 1303536 ***
https://bugs.launchpad.net/bugs/1303536
** This bug has been marked a duplicate of bug 1303536
Live migration fails. XML error: CPU feature `wdt' specified more than once
--
You received this bug notification because you are a member of
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1295876
Title:
libvirtError: internal error unable to add
Hi,
can you still reproduce this bug?
** Also affects: virtinst (Ubuntu)
Importance: Undecided
Status: New
** Changed in: virtinst (Ubuntu)
Status: New = Incomplete
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: virtinst (Ubuntu)
*** This bug is a duplicate of bug 1403841 ***
https://bugs.launchpad.net/bugs/1403841
** This bug has been marked a duplicate of bug 1403841
libvirt snapshot does not save source in xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks for the update.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1283179
Title:
Initialization of
Hi,
just to be clear, the backport.patch which you uploaded actually
increased jitter for you, making the situation worse, right?
--
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/1297218
Please file a new bug against the linux package, preferably (if
possible) using the command 'ubuntu-bug linux'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
KVM
Thierry,
Could you comment on whether this upstream patch
https://github.com/numactl/numactl/commit/32075635db57c3d5efe12f8fb569af857e01ccad
would suffice for you?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
We are working around important functionality being missing from
the kernel. I'd prefer that the apparmor mount functionality go
upstream sooner, rather then spend time (and risk regressions)
working around it better.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: qemu (Ubuntu)
Status: New = Invalid
** Changed in: qemu
Status: New = Invalid
--
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/1318830
Title:
High CPU
@vorlon,
I'll look a bit more and then do that (or reject).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.launchpad.net/bugs/1358835
Title:
numa_node_of_cpu() returns warning when cpu_index 79
You need to specify a template for the container to create. For
instance,
lxc-create -t download -n buildbox -- -d ubuntu -r trusty -a amd64
In newer releases, you do get a better error message:
# lxc-create -n b1
A template must be specified.
Use none if you really want a container without a
Your kernel does not have the apparmor patchset to support mount
restrictions. So long as tha tis the case, your workaround is the
correct one. Note that (privileged) containers are less secure this
way, although unprivileged containers should be ok.
** Changed in: lxc (Ubuntu)
Status:
Thanks, that definately should be fixed if possible.
status: triaged
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Thanks, patch merged upstream.
** 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/1339781
Title:
centos 7 needs setpcap
The fix is in lxc git HEAD. It should show up in lxc 1.1 soon.
** 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.
Sounds good, thanks.
--
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/1404396
Title:
[regression] vgabios - seabios breaks (my) 16-bit applications
To manage notifications about this
So is the patch in
http://www.seabios.org/pipermail/seabios/2015-January/008546.html the
one which definately fixes it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
** Changed in: libvirt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1034661
Title:
Translation item 1824 makes no sense
To
The name service xml section has gotten pretty expressive. See
'Addressing' at 60% into http://libvirt.org/formatnetwork.html.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This should be fixed as of 1.2.8-0ubuntu13
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1307436
Title:
If you are able to reproduce this with libvirt from the archive, please
re-open this bug.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Thanks for the update.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1327021
Title:
regression in snapshot
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
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/1411575
Title:
Thanks for the update. I will mark this 'invalid' meaning cannot be
reproduced now.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Finally, on my host I get:
root@srv-Ub1404:~# ps -ef | grep dnsmasq
lxc-dns+ 11309 1 0 Jan15 ?00:00:00 dnsmasq -u lxc-dnsmasq
--strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file=
--listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254
** Package changed: qemu-kvm (Ubuntu) = qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1408692
Title:
Could you show the results of:
strings /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0 | grep libusb_get_p
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Just to be sure you do also get this error if you just type
/usr/bin/qemu-system-x86_64 -vnc :1
?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1408692
Title:
libvirt does not
Is this still an issue for you?
There were some actual KSM corruption bugs which were somewhat recently
fixed.
KSM in general wil use more CPU in order to reduce memory contention, so
your results are not necessarily unexpected. Aside from turning KSM
off, you can also reduce the KSM frequency.
If you are still having an issue, please reply.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
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/1256866
Title:
This sort of result is not unexpected when the guest is under high load,
depending on your setup and whether the nics are emulated.
Can you show your kvm command line?
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided =
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
If this is still an issue, please try to reproduce it with the lastest
upstream daily build from https://launchpad.net/~ubuntu-
virt/+archive/ubuntu/virt-daily-upstream
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
The file seems to be in qemu-system-common (at least in Ubuntu 14.10).
The next question is how to best help the user to run the right command.
Should it go into the manpage?
** Package changed: qemu-kvm (Ubuntu) = qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
**
Please reply if you can still reproduce this bug.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
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
** Changed in: qemu (Ubuntu)
Status: New = Invalid
** Changed in: qemu
Status: New = Invalid
** Changed in: virtinst (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Thanks - just to be clear, was ther eany downside to setting
CONFIG_VGA_ALLOCATE_EXTRA_STACK=n?
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Importance: Medium = High
--
You received
** Changed in: qemu (Ubuntu)
Importance: Undecided = Low
** Changed in: qemu (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1396497
Title:
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1318830
Title:
High CPU usage on windows virtual machine
To manage
** Description changed:
+
+ Impact: unable to specify nic boot order
+ Test Case: use the xml below to create a VM, and check that the 'boot order'
is ignored.
+ Regression potential: This cherrypicks 4 patches from
@gema,
please re-do the 'apport-collect 1413540' (with the new, corrected
package names)
** 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 in Ubuntu.
Where did you get the custom kernel?
How exactly are you starting the container? What do you see when you
run
sudo lxc-checkconfig
? Please run 'lxc-start -n containername -l trace -o debug.out' and
attach 'debug.out'.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status:
Bug may not be in the kernel package, but it seems very unlikely to be
in cgmanager, and more clueful people are likely to see it this way.
** Package changed: cgmanager (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
You received this bug
Thanks for the information. To be clear, if you now 'sudo apt-get purge
librbd-dev', does it then fail again?
The librbd-dev package should only contain files needed for building
against librbd, not files needed for using librbd1. So if the answer to
the above question is yes then we should
** Changed in: libvirt (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1121933
Title:
umountroot remounts partition readonly when called
Please contact the owner of the PPA. It could also be helpful to test
libvirt from the archive (1.2.12-0ubuntu2) and see if that also
reproduces the startup error. If it does, then please reply here.
(marking invalid as this bug is in a ppa version of the package)
** Changed in: libvirt
Quoting Christopher Townsend (christopher.towns...@canonical.com):
Hi Serge,
Ok, I understand I can fix this issue by adding that line in my config.
However, my gripe now with this is that my configuration was working
with no issues prior to an update in LXC, then it broke for no apparent
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1419855
Title:
Looks like libnuma is not supported on arm. That complicates the
enablement.
--
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/1417937
Title:
qemu appears to be built without
Yup, we should be able to do Build-depends: libnuam-dev [ x86 arm64 ...
]
I will test something along those lines tomorrow.
--
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/1417937
Since this should be fixed by the new libvirt release now in vivid,
marking fix-released.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Quoting Chris Friesen (chris.frie...@windriver.com):
One could argue that the NUMA functionality wasn't intentionally turned
off (it was inherited from debian) and thus re-enabling it would be
fixing a bug.
That would definitely be the case if it had been on in precise or trusty,
but that
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1417937
Title:
qemu appears to be built without
** Changed in: qemu (Ubuntu Utopic)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1417937
Title:
qemu appears to be built without CONFIG_NUMA defined
** Description changed:
+ ===
+ SRU Justification
+ 1. Impact: openstack cannot use numactl to pin kvm to cpus
+ 2. Test case: ldd /usr/bin/qemu-system-x86* | grep numa
+ 3. Regression potential: this causes qemu to be build against
Quoting li,chen (chen...@intel.com):
would this be back-port to utopic ?
It's a new features, so doesn't strictly fall under SRU guidelines.
(See https://wiki.ubuntu.com/StableReleaseUpdates)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
importance: high
assignee: serge-hallyn
** Changed in: lxc (Ubuntu)
Importance: Low = High
** Changed in: lxc (Ubuntu)
Status: Fix Released = Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because
That's all very mysterious... :( Thanks for the update.
** Changed in: cgmanager (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
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/897750
Title:
libvirt/kvm problem with disk
qemu in 15.04 is currently 2.1, and will be 2.2 soon.
12.04 will not be getting a newer version.
I'm not sure where you realy wanted to file this bug, since obviously
you wanted a newer qemu-kvm in some version of Mint.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Fix Released
--
You
Probably not related to issue 406, as this is a debian 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/1414771
Title:
Can not clone lxc container with lvm backingstore after
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = 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/1414771
Title:
Can
Patch to fix this has been posted to the mailing list.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1414771
Title:
Can not clone lxc container with lvm backingstore after ubuntu
I've uploaded a test package to ppa:serge-hallyn/virt. Could you please
test whether that fixes the issue for you?
** No longer affects: libvirt (Ubuntu Precise)
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because
I'm not sure what comment #20 was about - the fix analogous to the
attached patch is adff345e1ec9a6f528731ae40168a76b8e7620e0 (which is
upstream).
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance:
1.2.8-0ubuntu12 should be made avalable through the cloud archive. But
I will mark this as affecting utopic and aim to add it to the next SRU
round.
** Also affects: libvirt (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Utopic)
Importance:
This has been discussed before. I definately want to make things work
as cleanly as possible out of the box. There are a few problems with
doing htis though, 1) networkmanager isn't the only place we'd need to
do this (most serious lxc hosts probably don't run networkmanager), 2)
if we do this
If this could be fixed in seabios that would be ideal. Discussion of a
second-best solution should probably wait unti lwe're certain that is
not possible.
Since with respect to this issue we should be in sync with Debian, I'm curious
whether Debian also has this issue.
--
You received this bug
1 - 100 of 6024 matches
Mail list logo
