[Bug 1089105] Re: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid
There is no this problem under Trusty (14.04), since the udev has
removed the below keymap:
ENV{DMI_VENDOR}==LENOVO, ATTR{[dmi/id]product_version}==*Lenovo
V480*, RUN+=keymap $name 0xf1 f21
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1089105
Title:
[Lenovo V480c Notebook]: Trackpad doesn't work after closing and
opening the lid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1089105/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1089105] Re: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid
In the latest ubuntu precise (12.04.5), the udev version is 175-0ubuntu9.8, and the keymap in the #31 still exists in this version udev, so this problem still happens on the V480c machines with latest ubuntu precise installed. But this is not a linux kernel bug, I think it is a lightm defect, and can be workaround through udev keymap rules. And since we already have 14.04LTS and there is no this problem in the 14.04 and onwards version, set won't fix for precise (12.04). ** Changed in: linux (Ubuntu Precise) Status: In Progress = Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1089105 Title: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1089105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396497] [NEW] 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot
Public bug reported: qemu-img _may_ be working as designed, but it feels like this could be a bug. I'd certainly prefer to only allow unique snapshot names (unless maybe something like a --force-non-unique-snapshot-names was also specified). If this really is correct behaviour, it should be documented as qemu- img(1) currently specifies no details whatsoever regarding expected behaviour or valid snapshot names. $ qemu-img snapshot -l image.cow $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow $ Note also how snapshot deletion works in reverse order - the oldest snapshot with a given name is deleted first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 2.1+dfsg-4ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 26 08:28:16 2014 InstallationDate: Installed on 2014-04-11 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 719 2 0.0 [kvm-irqfd-clean] MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to vivid on 2014-05-08 (201 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1396497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1346734] Re: Unprivileged LXC containers don't work under systemd
I created a per-user container t1, and confirm that it does start under upstart/cgmanger and doesn't under systemd. I now have a preliminary patch for putting the user slices into all cgroup controllers, plus some hand-crafted chown ubuntu for all the user-1000.slice cgroup directories so that they become writable (this part still needs to be added to the patch). I understand that this should now be sufficient: ubuntu@ulxc$ cat /proc/$$/cgroup 10:devices:/user.slice/user-1000.slice 9:memory:/user.slice/user-1000.slice 8:cpuset:/ 7:hugetlb:/user.slice/user-1000.slice 6:blkio:/user.slice/user-1000.slice 5:cpu,cpuacct:/user.slice/user-1000.slice 4:freezer:/user.slice/user-1000.slice 3:perf_event:/user.slice/user-1000.slice 2:net_cls,net_prio:/user.slice/user-1000.slice 1:name=systemd:/user.slice/user-1000.slice/session-1.scope ubuntu@ulxc:~$ ls -ld /sys/fs/cgroup/*/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/blkio/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/cpuacct/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/cpu,cpuacct/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/cpuset/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/cpu/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/devices/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/freezer/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/hugetlb/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/memory/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/net_cls,net_prio/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/net_cls/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/net_prio/user.slice/user-1000.slice/ drwxr-xr-x 2 ubuntu root 0 Nov 26 10:41 /sys/fs/cgroup/perf_event/user.slice/user-1000.slice/ drwxr-xr-x 4 root root 0 Nov 26 10:33 /sys/fs/cgroup/systemd/user.slice/user-1000.slice/ I'm not sure why my login shell isn't in cpuset, I'll debug that still. But I chown'ed /sys/fs/cgroup/cpuset/ to ubuntu as well. But still lxc-start fails: $ lxc-start -n t1 -F lxc-start: cgfs.c: lxc_cgroupfs_create: 849 Could not set clone_children to 1 for cpuset hierarchy in parent cgroup. lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset//user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset//user.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/ lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu,cpuacct/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/user.slice/user-1000.slice lxc-start: cgfs.c: cgroup_rmdir: 207 Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/net_cls,net_prio/user.slice/user-1000.slice lxc-start: start.c: lxc_spawn: 864 failed creating cgroups Questions: - Why is it trying to *remove* the existing cgroups? It sounds wrong to fuzz around with those, I thought it would merely want and need to create new cgroups below those? And the ubuntu user can definitively do that: ubuntu@ulxc:~$ mkdir /sys/fs/cgroup/cpu,cpuacct/user.slice/user-1000.slice/mygroup ubuntu@ulxc:~$ ls -ld /sys/fs/cgroup/cpu,cpuacct/user.slice/user-1000.slice/mygroup drwxrwxr-x 2 ubuntu ubuntu 0 Nov 26 10:50 /sys/fs/cgroup/cpu,cpuacct/user.slice/user-1000.slice/mygroup --logpriority debug --logfile /tmp/d doesn't really give much information either. stracing lxc-start only shows rmdir() whose errors are shown above, it doesn't have any mkdir() or similar call which would show an attempt to create new cgroups? ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of
[Bug 1396536] [NEW] lxc_start - Exec format error - failed to exec /sbin/init
Public bug reported: I have an up to date Ubuntu 14.04. I followed the guide at https://help.ubuntu.com/lts/serverguide/lxc.html sudo apt-get install lxc sudo lxc-create --template download --name u1 - Choose ubuntu-vivid-armhf, then: sudo lxc-start --name u1 --daemon lxc-start 1416996721.249 INFO lxc_apparmor - changed apparmor profile to lxc-container-default lxc-start 1416996721.249 NOTICE lxc_start - exec'ing '/sbin/init' lxc-start 1416996721.253 ERRORlxc_start - Exec format error - failed to exec /sbin/init lxc- $ sudo lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART u1STOPPED - - NO $ sudo lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.13.0-24-generic --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup clone_children flag: enabled Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig Except apt-get update and apt-get upgrade I didn't install any other packages (okay, I installed vim and git). ** Affects: lxc (Ubuntu) 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
In case it wasn't clear I followed instructions for basic privileged usage. not user namespaces. -- 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
$ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/init 541928 0 lrwxrwxrwx 1 root root 7 Nov 19 23:17 /var/lib/lxc/u1/rootfs/sbin/init - upstart $ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/upstart 541969 220 -rwxr-xr-x 1 root root 223596 Nov 19 23:17 /var/lib/lxc/u1/rootfs/sbin/upstart -- 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
$ sudo file /var/lib/lxc/u1/rootfs/sbin/upstart /var/lib/lxc/u1/rootfs/sbin/upstart: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=401fd3761e2edac12fc6081bebbfd834a985e11b, stripped -- 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396572] [NEW] Critcial security vulnerabilties in docker 1.3.2
*** This bug is a security vulnerability *** Public security bug reported: Today, we are releasing Docker 1.3.2 in order to address two critical security issues. This release also includes several bugfixes, including changes to the insecure-registry option. Below are CVE descriptions for the vulnerabilities addressed in this release. Docker 1.3.2 is available immediately for all supported platforms: https://docs.docker.com/installation/ Docker Security Advisory [24 Nov 2014] = = [CVE-2014-6407] Archive extraction allowing host privilege escalation = Severity: Critical Affects: Docker up to 1.3.1 The Docker engine, up to and including version 1.3.1, was vulnerable to extracting files to arbitrary paths on the host during ‘docker pull’ and ‘docker load’ operations. This was caused by symlink and hardlink traversals present in Docker's image extraction. This vulnerability could be leveraged to perform remote code execution and privilege escalation. Docker 1.3.2 remedies this vulnerability. Additional checks have been added to pkg/archive and image extraction is now performed in a chroot. No remediation is available for older versions of Docker and users are advised to upgrade. Related vulnerabilities discovered by Florian Weimer of Red Hat Product Security and independent researcher, Tõnis Tiigi. = [CVE-2014-6408] Security options applied to image could lead to container escalation = Severity: Critical Affects: Docker 1.3.0-1.3.1 Docker versions 1.3.0 through 1.3.1 allowed security options to be applied to images, allowing images to modify the default run profile of containers executing these images. This vulnerability could allow a malicious image creator to loosen the restrictions applied to a container’s processes, potentially facilitating a break-out. Docker 1.3.2 remedies this vulnerability. Security options applied to images are no longer consumed by the Docker engine and will be ignored. Users are advised to upgrade. = Other changes: = Besides the above CVEs, the 1.3.2 release allows administrators to pass a CIDR-formatted range of addresses for '—insecure-registry'. In addition, allowing a cleartext registry to exist on localhost is now default behavior. This change was made due to user feedback following the changes made in 1.3.1 to resolve CVE-2014-5277. ** Affects: docker.io (Ubuntu) Importance: High Status: Fix Committed ** Affects: docker.io (Ubuntu Trusty) Importance: High Status: New ** Affects: docker.io (Ubuntu Utopic) Importance: High Status: New ** Affects: docker.io (Ubuntu Vivid) Importance: High Status: Fix Committed ** Information type changed from Public to Public Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-6407 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-6408 ** Changed in: docker.io (Ubuntu) Importance: Undecided = High ** Also affects: docker.io (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Vivid) Importance: High Status: New ** Also affects: docker.io (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: docker.io (Ubuntu Vivid) Status: New = Fix Committed ** Changed in: docker.io (Ubuntu Utopic) Importance: Undecided = High ** Changed in: docker.io (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1396572 Title: Critcial security vulnerabilties in docker 1.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1396572/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384555] Re: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0
Reviewed: https://review.openstack.org/136710 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=467a4496cfcd74b473730d2baa667fd633e4d0b3 Submitter: Jenkins Branch:stable/juno commit 467a4496cfcd74b473730d2baa667fd633e4d0b3 Author: Jakub Libosvar libos...@redhat.com Date: Fri Oct 31 15:49:40 2014 +0100 Drop and recreate FK if adding new PK to routerl3bindings Since MySQL 5.6 FK columns cannot be altered. As a workaround we can drop the FK before ALTER COLUMN and then recreate it. Change-Id: Icd1b3075cf29a6b0c477a4ddea2e6ebee91baef8 Closes-Bug: 1384555 (cherry picked from commit b5f1cc48b877caaebc944154d56a8bb4060aa9b0) ** Tags added: in-stable-juno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396595] [NEW] Using virt-install fails on ppc64el with ERROR XML error: No PCI buses available
Public bug reported: Currently, if you don't specify the parameter --arch=ppc64 to virt- install, the virt-install will fail as follows: $ virt-install --name breno --memory 4096 --disk size=500,bus=virtio --cdrom mini.iso WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. Starting install... Allocating 'breno.qcow2' | 500 GB 00:04 ERRORXML error: No PCI buses available Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start breno otherwise, please restart your installation. On the other side, if the option --arch=ppc64 is passed, it works fine. I generated a diff of both XML generated in both cases, and the result is the following (with some unimportant parts removed): +type arch=ppc64 machine=pserieshvm/type boot dev=cdrom/ boot dev=hd/ /os @@ -19,33 +19,33 @@ on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices -emulator/usr/bin/qemu-system-ppc64le/emulator +emulator/usr/bin/qemu-system-ppc64/emulator disk type=file device=disk driver name=qemu type=qcow2/ driver name=qemu type=raw/ source file=/home/brenohl/versions/14.04.2/mini.iso/ - target dev=hda bus=ide/ + target dev=sda bus=scsi/ readonly/ /disk vcpu1/vcpu os -type arch=ppc64lehvm/type +type arch=ppc64 machine=pserieshvm/type boot dev=hd/ /os features @@ -58,19 +58,19 @@ on_rebootrestart/on_reboot on_crashrestart/on_crash devices -emulator/usr/bin/qemu-system-ppc64le/emulator +emulator/usr/bin/qemu-system-ppc64/emulator disk type=file device=disk driver name=qemu type=qcow2/ /disk disk type=block device=cdrom - target dev=hda bus=ide/ + target dev=sda bus=scsi/ readonly/ /disk I understand that libvirt should consider ppc64le a ppc64 guests for all purposes. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: ppc64el ** Tags added: ppc64el -- 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/1396595 Title: Using virt-install fails on ppc64el with ERRORXML error: No PCI buses available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1396595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393832] Re: Modules fail to enable when configured after apache2 is configured
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: Fix Committed = Fix Released -- 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/1393832 Title: Modules fail to enable when configured after apache2 is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1393832/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1358305] Re: harden default ssl settings
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: New = Fix Released -- 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/1358305 Title: harden default ssl settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1358305/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1312854] Re: dh-apache2 causes a postinst failure when a package depends on an apache2-bin provided module
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: Triaged = Fix Released -- 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/1312854 Title: dh-apache2 causes a postinst failure when a package depends on an apache2-bin provided module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1312854/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1366174] Re: apache2 SEGV with multiple SSL sites
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1366174 Title: apache2 SEGV with multiple SSL sites To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1366174/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1312533] Re: Installing apache2 fails in apache2.preinst when a previous version was in removed state
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: Triaged = Fix Released -- 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/1312533 Title: Installing apache2 fails in apache2.preinst when a previous version was in removed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1312533/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333388] Re: mod_ident no longer included in apache
This bug was fixed in the package apache2 - 2.4.10-8ubuntu2 --- apache2 (2.4.10-8ubuntu2) vivid; urgency=medium * Allow triggers-awaited and triggers-pending states in addition to installed when determining whether to defer actions or process deferred actions (LP: #1393832). -- Colin Watson cjwat...@ubuntu.com Wed, 26 Nov 2014 11:31:44 + ** Changed in: apache2 (Ubuntu) Status: Confirmed = Fix Released -- 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/188 Title: mod_ident no longer included in apache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1396536] [NEW] lxc_start - Exec format error - failed to exec /sbin/init
Hi, thanks for submitting this bug. Is your host architecture armhf? If not, then when using the download template you'll need to manually install qemu-user-static on the host, and copy /usr/bin/qemu-arm-static into the container's rootfs. The easier way to create such a container, currently, is still using the ubuntu template, which will link the qemu-user binary into your container for you. 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 subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
No my arch is amd64, that's why I specified -a armhf. I know about qemu (I wasn't sure whether to use static or binfmt), but errors should be meaningful, instead it seems as if lxc is working fine, but in fact it's not. Obviously it's not a matter of permissions, so the error is wrong. The image I used is downloaded from debian.org, so I didn't prepare it myself. Either non-armhf hosts shouldn't list armhf images or should warn (maybe in documentation, if not in code) that those aren't usable without additional packages. -- 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396670] [NEW] gdbsx missing
You have been subscribed to a public bug: The gdbsx debugging tool i smissing from the xen-tools package, or any other xen package, making debug difficult... ** Affects: xen (Ubuntu) Importance: Undecided Status: New -- gdbsx missing https://bugs.launchpad.net/bugs/1396670 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396670] Re: gdbsx missing
** Package changed: xen-tools (Ubuntu) = xen (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1396670 Title: gdbsx missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1396670/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
I agree it'd be nice for the download template to be clever and filter its output. However the fact that it's very very difficult to know what your CPU is actually capable of running (especially for arm64, armel, armhf and powerpc, powerpc64 and ppc64el) and the name for the architectures changes between distributions too. So for now, we expect our users to know what architecture their CPU is capable of running and then select something which has a chance to work. Marking bug report as low priority wishlist. ** Changed in: lxc (Ubuntu) Importance: Undecided = Wishlist ** 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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396724] [NEW] false kernel dependency in walinuxagent package
Public bug reported: walinuxagent has a false kernel dependency which prevents use of hwe kernel ** Affects: walinuxagent (Ubuntu) Importance: High Assignee: Ben Howard (utlemming) Status: Confirmed -- 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/1396724 Title: false kernel dependency in walinuxagent package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1396724/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396724] Re: false kernel dependency in walinuxagent package
** Description changed: - walinuxagent has a false kernel dependency which prevents use of hwe - kernel + [IMPACT] Windows Azure users are unable to remove the 3.13 Trusty kernel + infavor of the HWE enablement kernel without removing walinuxagent. + Microsoft is suggesting that users + + [FIX] Remove the dependency on linux-image-virtual. The dependency is + completely false. + + [TEST CASE 1] + - Boot image in Azure + - Install walinuxagent from proposed + - Run sudo apt-get -y purge linux-image-virtual linux-image-extra-virtual + - Confirm that walinuxagent is still installed + + [TEST CASE 2] + - Build image from -proposed + - Confirm that walinuxagent is installed and that host provisions + + + walinuxagent has a false kernel dependency which prevents use of hwe kernel -- 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/1396724 Title: false kernel dependency in walinuxagent package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1396724/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396740] [NEW] etherwake does not wake up machines
Public bug reported: wakeonlan uses a tcp socket to wake up the server and can run as the maas user. ether_wake uses a udp socket to wake up the server and must run as root for it to work. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1396740 Title: etherwake does not wake up machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1396740/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396740] Re: etherwake does not wake up machines
The fix for this is ato add the following line to /etc/sudoers.d/99 -maas-sudoers: maas ALL= NOPASSWD: /usr/sbin/etherwake and edit /etc/maas/templates/power/ether_wake.template to change: /usr/sbin/etherwake $mac_address to: sudo /usr/sbin/etherwake $mac_address If the network that you need to send to is not eth0 then you need to use the following instead: sudo /usr/sbin/etherwake -i ethx $mac_address -- 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/1396740 Title: etherwake does not wake up machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1396740/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396724] Re: false kernel dependency in walinuxagent package
** Description changed: [IMPACT] Windows Azure users are unable to remove the 3.13 Trusty kernel infavor of the HWE enablement kernel without removing walinuxagent. Microsoft is suggesting that users [FIX] Remove the dependency on linux-image-virtual. The dependency is completely false. [TEST CASE 1] - Boot image in Azure - Install walinuxagent from proposed - Run sudo apt-get -y purge linux-image-virtual linux-image-extra-virtual - Confirm that walinuxagent is still installed [TEST CASE 2] - - Build image from -proposed + - Build image from -proposed and the linxu-virtual-lts-utopic kernel - Confirm that walinuxagent is installed and that host provisions - - walinuxagent has a false kernel dependency which prevents use of hwe kernel + walinuxagent has a false kernel dependency which prevents use of hwe + kernel -- 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/1396724 Title: false kernel dependency in walinuxagent package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1396724/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360655] Re: SRU for clamav on intrepid (freshclam apparmor profile updates)
*** This bug is a duplicate of bug 359301 *** https://bugs.launchpad.net/bugs/359301 ** This bug has been marked a duplicate of bug 359301 klamav can't download virus database on jaunty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/360655 Title: SRU for clamav on intrepid (freshclam apparmor profile updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/360655/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 359301] Re: klamav can't download virus database on jaunty
** Changed in: clamav (Ubuntu Intrepid) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/359301 Title: klamav can't download virus database on jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/359301/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Ok I think I can reproduce this; after running some disk operations (bonnie++ and split a 100MB file), if I shutdown and try to boot the VM the disk cannot be booted and I'm presented with the grub menu. However this reproducer is not yet 100% reliable. Next week I'll work on bisecting it down after testing latest upstream. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Awesome - thank you Chris. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396497] Re: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot
I'd agree that at least the last part - removing the oldest snapshot first - seems like a bug. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1396497 Title: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1396497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1356478] Re: kvm_stat not found in qemu packages
Please see the discussion in the debian bug (https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=758042). -- 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/1356478 Title: kvm_stat not found in qemu packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1356478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu Utopic) 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu Trusty) 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1392781] Re: qemu-kvm is missing for ppc64el
*** This bug is a duplicate of bug 1389897 *** https://bugs.launchpad.net/bugs/1389897 Which release are you using? qemu-kvm currently exists only for vivid, but I believe that change may end up SRUd for trusty. I'm going to mark this bug as a duplicate of 1389897 which is where this was actually fixed. ** This bug has been marked a duplicate of bug 1389897 no way to install enough qemu for kvm in a cross platform way -- 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/1392781 Title: qemu-kvm is missing for ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1392781/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
