Thanks for the information. Looks like we can apply these in debian
too.
** Also affects: qemu (Ubuntu Utopic)
Importance: High
Status: Triaged
** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
I'm marking this low priority per guidelines since there is a workaround
(use virsh define). However it most certainly looks like a bug,
especially since --autodestroy is listed as an option in the help
usage.
** Summary changed:
- Vm destroyed when created virsh create without --autodestroy
+
The minimal PATH comes from
getconf -a | grep ^PATH
(if confstr were not available then lxc would actually default to a
longer PATH)
status: invalid
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
I'm saying this is not a bug because the limited path is by design. Your
system in fact is telling lxc which path to use as the default.
If you think that rather than take the value from the system through sysconf,
we should always use a longer PATH, then that could be discussed on the
lxc-devel
Looks like the value actually comes straight from a #define in the glibc
source code.
As such, I think it would be pretty reasonable to change lxc to always
use its own path.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: Invalid =
affects: ubuntu/qemu
importance: high
affects: qemu
importance: high
** Also affects: qemu (Ubuntu)
Importance: High
Status: New
** Also affects: qemu
Importance: High
Status: New
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you
Public bug reported:
Currently if you run a container with lxc-container-default-with-
nesting profile, you can run privileged containers inside that, but not
unprivileged containers. The special cases we add for /var/lib/lxc
should also be added for $HOME/.local/share/lxc.
** Affects: lxc
Public bug reported:
The lxc-user-nic program is a setuid-root program to create veth nics
and hook them to the host bridge and unprivileged containers. It should
run under a very tight apparmor profile.
(Make sure to test with ovs bridges as well, as its call-out to ovs-
vsctl may have
A proposed fix has been sent to the mailing list, and will probably be
applied in utopic today. In the meantime you can work around this by
using the 'append_config_item' method instead of set_config_item. (Note
that the C API does not have this same behavior, so this is only for the
python
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** 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/1376717
Title:
** Changed in: lxc (Ubuntu)
Status: New = 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/1357103
Title:
apparmor denied a golang build inside a container
To manage
Thanks. This'll need to be fixed in the lxc.preinst.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** 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
** 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/1355813
Title:
LXC containers reset bridge MTU on start/restart
To manage
Thanks for the bug report and the patch. I'm a bit concerned about
supporting this. I understand why you want it, but lxc in general won't
work well with a read-only cache, so an install failure early on would
seem preferable to a lxc-create failure later on.
Would using an overlayfs of the
It actually seems like a bug in aa-status.
Note that /sys/kernel/security/apparmor/profiles is not readable by non-
root users on the host. Yet non-root users on the host do not see a
python traceback when they run 'aa-status --enable'. This also suggests
that a container should not provide
Thanks for reporting this bug. To fix the cgmanager issue, add the line
lxc.mount.auto = cgroup:mixed
to your container configuration file.
That shouldn't explain your hang however. Assuming it doesn't, please
run
lxc-start -n container -l trace -o debug.out -- /sbin/init debug
verbose
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
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/1324393
Title:
Force off fails with Permission denied after
Thanks for submitting this bug
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Description changed:
+ =
+ Impact: qemu VMs cannot be migrated from 12.04-14.04 hosts
+ Test Case: migrate a vm from p-t host, using disk on a NFS share. On the
14.04 host, use
+ kvm -M pc-1.0-precise [...] -incoming tcp:0.0.0.0:
+ and on the
Quoting Nikola Krzalic (nik...@krzalic.com):
Looks like the lxc-start command got stuck, after killing the process
everything went back to normal.
...
still, I find it a bit strange that not even lxc-ls was working properly
Right, we should find a way to keep lxc-stop and lxc-ls from
Using the ipxe-precise package from ppa:serge-hallyn/qemu-migration2,
migration from 12.04-14.04 (using -proposed for both) succeeded. I
also ran a full test-qemu.py from lp:qa-regressoin-testing with no
errors.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
thanks for reporting this bug.
Could you please show:
1. The result of 'netstat -x | grep lxc'
2. ps -ef | grep lxc
status: incomplete
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
We've discussed this in #ubuntu-release and decided to not support the
pc-1.0-precise machine type after 14.04. Therefore the utopic (FFE) bug
is wontfix, and we will only seek SRU for 14.04.
** Changed in: qemu (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification
** Package changed: lxc (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Description changed:
+ =
+ ec2-run-instances ami-3021fb58 -t m1.small
+
+ ssh into the instance,
+
+ sudo ip link add type veth
+
+
Build log is at: https://launchpad.net/~serge-hallyn/+archive/ubuntu
/qemu-migration2/+build/6413926/+files/buildlog_ubuntu-utopic-
amd64.qemu_2.1%2Bdfsg-4ubuntu5%7Emigration3_UPLOADING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
installed, 0 to remove and 62 not upgraded.
Need to get 2,033 kB of archives.
After this operation, 22.5 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/serge-hallyn/qemu-migration2/ubuntu/ utopic/main
qemu-system-x86 amd64 2.1+dfsg-4ubuntu5~migration3 [2,033 kB]
Fetched 2,033 kB
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Precise)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu Trusty)
** No longer affects: libvirt (Ubuntu Precise)
--
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/1375910
Title:
package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade:
Thanks for submitting this bug.
To be clear,
'sudo ip link add type veth'
also returns an error?
Could you tell us which ami and which machine type you used to start the
amazon instance?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
Public bug reported:
Bug 1291321 shows that qemu VMs cannot be migrated from a host running
12.04 to a host running 14.04.
https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution.
As a part of this, we need to define the pc-1.0-precise machine type
which can accept incoming
** Description changed:
Bug 1291321 shows that qemu VMs cannot be migrated from a host running
12.04 to a host running 14.04.
https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution.
As a part of this, we need to define the pc-1.0-precise machine type
which can accept
Public bug reported:
Bug 1291321 shows that qemu VMs cannot be migrated from a host running
12.04 to a host running 14.04.
https://wiki.ubuntu.com/QemuPTMigration explains the proposed solution.
One part of the problem is that libvirt in trusty cannot distinguish a
pc-1.0 machine being migrated
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu Precise)
Importance: Undecided = High
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks I'll do some testing. I suspect we'll need to allow access to
cgmanager, but otherwise this looks good.
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member
Since you're not restricting dbus, cgmanager is actually unaffected, so
this shouldn't restrict nested use at all.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Triaged
--
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 for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[serge-hallyn] convert libvirt to cgmanager (4d): DONE
[racb] Early cycle merge report: POSTPONED
[serge-hallyn] merge qemu: DONE
Work items for ubuntu-14.07:
[serge-hallyn] cgmanager package
Updated init patch which I'll be pushing.
--- haproxy.old 2014-09-22 10:52:07.599718882 +
+++ haproxy.new 2014-09-22 10:51:34.815653158 +
@@ -46,7 +46,9 @@
return 0
fi
for pid in $(cat $PIDFILE) ; do
- /bin/kill $pid || return 4
+
** Description changed:
+
+ SRU Justification:
+ Impact: 'service haproxy stop' returns 4 if haproxy was already stopped.
+ Development fix: check whether haproxy is running before trying to kill it
+ Stable fix: same as development fix
+
** Changed in: haproxy (Ubuntu Precise)
Importance: Undecided = High
** Changed in: haproxy (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
** Also affects: libvirt-python (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt-python (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt-python (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are
@Raphael,
if you're having trouble with the virtio network type, then it sounds
like either you are not passing the romfile option to qemu in the trusty
host (-global virtio-net-pci.romfile=pxe-virtio.rom.12.04), or you do
not have the pxe-virtio.rom.12.04 file installed (in /usr/share/qemu/ as
a
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
On my main server (3.13.0-32-generic with precise userspace) I installed
a trusty container with ext3 (LVM) backing store. There I installed uvt
and created 4 VMs, 2 precise amd64 and 2 precise i386. I several times
did:
ubuntu@uvttest:~$ cat list
p-precise-server-amd64
p-precise-server-i386
** Changed in: libvirt-python (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt-python in Ubuntu.
https://bugs.launchpad.net/bugs/1367425
Title:
[FFE] Upgrade to 1.2.8
To manage
We can become more clever about the packaging later, but this proposed debdiff
should
1. clean up the old qemu-system-x86 sysvinit job
2. install a qemu-kvm upstart job on ppcc64le
** Patch added: d1.debdiff
Thanks, the new version fixed the bug.
** 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 qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1324174
Title:
qemu should
** Changed in: libvirt (Ubuntu)
Status: In Progress = 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/1331081
Title:
please split libvirt-driver apparmor
Seems like the best thing would be to move qemu-system-x86.qemu-
kvm.upstart to qemu-system-common.qemu-kvm.upstart (and same with
.default and .init) and have the jobs check for the right architectures.
** Changed in: qemu (Ubuntu)
Status: New = Triaged
** Changed in: qemu (Ubuntu)
Quoting Raphael Thoma (raphit...@gmx.ch):
In the meantime I could find out that the problem only pops up when
virtio (or virtio-net) is being used for network devices. With the
e1000 nic_type everything is working as expected. Can this be seen as
related to this bug?
Perhaps, but if so then
** Changed in: qemu (Ubuntu)
Importance: Medium = 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/1369785
Title:
kvm modules not autoloaded on ppc64el
To manage notifications
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New = Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
Thanks for submitting this bug. Indeed we should re-set the trusty
machine type to point to 2.0.
We could introduce a utopic machine type, but since utopic won't be
supported at the next LTS I'm thinking of not doing so.
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[serge-hallyn] convert libvirt to cgmanager (4d): DONE
[racb] Early cycle merge report: POSTPONED
[serge-hallyn] merge qemu: DONE
Work items for ubuntu-14.07:
[serge-hallyn] cgmanager package
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[tycho-s] test/fix basic multi-process criu: DONE
[tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE
[tycho-s] c/r cgroup settings: DONE
[serge-hallyn] fix btrfs issues with lxc
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 qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1368439
Title:
Random high latency with KSM
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: 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/1368439
Title:
Random high
Sadly this fix isn't quite right. The reason is that the modprobe
file is qemu-system-x86.modprobe, but the postinst doing the reload
of kvm_intel is qemu-system-common.postinst.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
I've 'fixed' the fix in utopic, so can post a new fix to trusty once
2.0.0+dfsg-2ubuntu1.4 is kicked out of the archive.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks. Meanwhile I've raised the issue on lxc-devel 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/1367730
Title:
container root directory has broken permissions with
It appears your local copy of the package is corrupted:
Unpacking qemu-system-misc (2.0.0+dfsg-2ubuntu1.3) over
(2.0.0+dfsg-2ubuntu1.2) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed
data is corrupt
Please try the following:
sudo apt-get clean
sudo apt-get
Thanks @msaxl, I'll add this patch to our package.
** Changed in: samba (Ubuntu Utopic)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1310919
Thanks. so those should be fixed in the 1.2.8 version we are trying to
upload (awaiting FFE) to utopic now. Note also that commit 7eabd55.
introduced a regression fixed by c285ffc4.
We can SRU these into trusty once they are in utopic.
** Also affects: libvirt (Ubuntu Precise)
Importance:
** Also affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cgmanager (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
** Changed in: cgmanager (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
[FFE] Implement AbandonScope (etc)
To
Thanks for reporting this bug. I'm not sure it's actually a dup of
1240757, because the syslog seems to indicate that dnsmasq is offering
addresses over lxcbr0.
Could you do 'lxc-start -n container0 -l trace -o debug.out' and attach
debug.out here?
** Changed in: lxc (Ubuntu)
Status: New
** 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/1367730
Title:
container root directory has broken permissions with tight
It looks like the patch was accidentally dropped from series two merges
ago, and in the last merge was dropped for not being in series.
However, the deeper problem is that the patch hasn't made it upstream.
Looking at the upstream bug, in fact, the proposed fix has changed a
bit.
Would someone
Thanks, we can combine this SRU with bug 1324174.
--
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/1366868
Title:
kvm: dompmwakeup fails if domain becomes pmsuspended
To manage
Public bug reported:
The lastest libvirt release is 1.2.8. This includes a number of
bugfixes and memory leaks since 1.2.6. Uploading this to Utopic will
make backporting of bug-fixes in SRUs easier.
The lp:qa-regression-testing scripts/test-libvirt.py has been run
against this package,
** Changed in: libvirt-python (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt-python in Ubuntu.
https://bugs.launchpad.net/bugs/1287841
Title:
FFE: libvirt-python 1.2.2
To manage
Public bug reported:
This will be needed for libvirt-python to match libvirt if the libvirt
FFE for 1.2.8 (bug 1367422) is approved.
The changelog follows:
2014-09-01 Pavel Hrdina phrd...@redhat.com
Implement API bindings for virDomainBlockCopy
2014-09-01 Pavel Hrdina
** Description changed:
- Otherwise user may be confused as to why nesting is not enabled until a
+ Otherwise user may be confused as to why nesting is not enabled until a
reboot.
+
+ SRU Justification:
+ 1. Impact: Users who install a new intel-baesd machine and immediately start
+ a VM will
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[serge-hallyn] convert libvirt to cgmanager (4d): DONE
[racb] Early cycle merge report: POSTPONED
[serge-hallyn] merge qemu: DONE
Work items for ubuntu-14.07:
[serge-hallyn] cgmanager package
This is interesting. The apparmor policy includes the rule:
owner /run/shm/spice.* rw
/dev/shm is a symlink to /run/shm, so you should have the
needed permissions. Could you please show the results of
ls -ld /run/shm /dev/shm
ls -l /run/shm /dev/shm
status: incomplete
** Changed in: qemu
Fascinating - thanks. So we should double up on those rules.
** Changed in: qemu (Ubuntu)
Status: New = Triaged
** Summary changed:
- apparmor breaks virt-manager creation [qemu-system-x86_64 crashed with
SIGABRT in spice_logv()]
+ libvirt-qemu profile needs /dev/shm/spice-* rule for
** Package changed: qemu (Ubuntu) = libvirt (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/1365163
Title:
libvirt-qemu profile needs /dev/shm/spice-* rule for systemd hosts.
** 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/1287840
Title:
FFE: libvirt-1.2.2
To manage notifications
There are 69 commits to block/qcow* between 1.5.0 and 1.7.0.
I have compiled binaries of qemu-system-x86_64 and qemu-img
at each of those commits and pushed them to
http://people.canonical.com/~serge/binaries.0
through
http://people.canonical.com/~serge/binaries.68
Note that binaries.0 is the
*** This bug is a duplicate of bug 1346815 ***
https://bugs.launchpad.net/bugs/1346815
** This bug has been marked a duplicate of bug 1346815
lxc-clone causes duplicate MAC address and IP address
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
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/1363063
Title:
ACPI BIOS Error with 3.13.0-32-generic and qemu
affects: apparmor
** Also affects: apparmor
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/1350947
Title:
apparmor: no working rule to
@Raphi,
You say you started the instance with -machine pc-1.0. To accept incoming
migration from precise you must use -machine pc-1.0-qemu-kvm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Please show us the contents of /var/log/apt/term.log, /etc/lsb-release,
/etc/lxc/lxc-net.conf, /etc/default/lxc*, /usr/sbin/policy-rc.d, and the
results of 'uname -a', 'dpkg -l | grep lxc', and 'ls -l /sbin/init'.
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** 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/1347020
Title:
On the qemu-ppc and qemu-devel mailing lists the following query was made about
the non-packaging changes:
So before we add anything to QEMU, I would like to first see someone
point me to kernel patches that actually enable LE on Linux for 32bit
user space. So far I'm not aware of any (and I
Please make sure that lxc.kmsg = 0 in your container configuration file
for systemd guests.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1347020
Title:
trusty host - utopic
Thanks for submitting this patch. I'll aim to get it into 14.10 and
14.04. Is there a particular way you'd recommend testing this, or
should i simply download the ppc64le 14.10 cd image and try chrooting
into it?
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu
Hi Jamie,
just to make sure, did you permanently disable ksm? Does
cat /sys/kernel/mm/ksm/run
still show 0?
I've so far never seen a case where a reboot did not fix the issue,
nor have I seen an issue (other than suspending the host sometimes
causing the VM to hang so that I have to destroy
Ok - thanks Jamie.
--
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/1292234
Title:
qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
To manage notifications about this bug
libvirt searches at startup for one of the kvm-img and qemu-img
commands. If the kvm-img command goes away while libvirt is running,
then it continues to try to use kvm-img, and this error occurs.
Restarting libvirt is therefore a workaround.
The kvm-img command has not existed since early in
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1261338
Title:
lxc-stop and even lxc-stop -k can hang
To manage
@Andreas,
yes that's definately what it sounds like.
--
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/1357103
Title:
apparmor denied a golang build inside a container
To manage
Perhaps i don't understand what you are doing.
My understanding was that a package is being built (in the buildds)
under qemu. Qemu is failing due to tcg failure. We want to tes
twhether a qemu patch fixes it.
That's why I suggest installing the new qemu package on your host, using
it to run a
Thanks for the information. Indeed, lxc-stop -k still works by talking
to the lxc monitor. What appears to have happened here is that the
monitor itself is frozen.
Could you please show full output of:
ps -ef
Then do 'ps -ef | grep lxc-start' to find the lxc-start process for the
hung
Hi James,
does setting lxc.network.mtu = 9000 in the container configuration file
work?
Depending on how juju creates the containers, you may be able to simply
add that line to the bottom of /etc/lxc/default.conf to get the desired
result.
--
You received this bug notification because you are
Hi Dann,
yeah, thanks - let's mark this fixed and open a new one.
** Changed in: qemu
Status: New = Fix Released
** Changed in: qemu (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
901 - 1000 of 6024 matches
Mail list logo
