[FFE] Qemu 2.10 in Artful

Bug #1699968 reported by Christian Ehrhardt 
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Hi,
there is no Qemu 2.10 released yet, but we know this will be a tight schedule so I want to inform the release Team as early as possible.

There are multiple reasons to
- more HW support for several things that come out new
- Smaller Jump from 17.10 to 18.04 later on
- General Updates and Fixes

The Planning schedule is now upstream [1] and therefore obviously there are no build logs for the FFE so far, yet we a plan to mitigate this being a too huge risk.

The plan is to start peparing packaging, testing and qualification with tag -rc0 end of July.
Also we work on Qemu 2.9 as an interim upload to include all packaging changes we intent for this cycle to make 2.10 "only" a rebase then.

I'll come back here once we have the earliest reviewable content.

[1]: http://wiki.qemu.org/Planning/2.10

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Subscribing ubuntu-release now to get early feedback, if none is needed/available please unsubscribe yourself and I'll resubscribe you once I have the first Data of 2.10-rc0 packaging we intent to use as preview.

Changed in qemu (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

To be clear, the Plan to prep 2.9 and start on 2.10-rc0 includes the potential of falling back to 2.9 if stability/testing comes to the conclusion that 2.10 isn't ready enough.

Revision history for this message
Breno Leitão (breno-leitao) wrote :

Thanks Christian, I support this decision from an IBM point of view. This FFE will avoid us doing backport of POWER9 virtualization from 2.10 to 2.9.

tags: added: upgrade-software-version
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Breno, as long as it is clear that this comes under the "as good as possible, but might fall back to 2.9" as outlined above I'm happy that this helps you.

tags: added: virt-fixed-by-2.10
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Testing on 2.10-rc2 (latest atm) looks very good with only one hickup left that is currently discussed upstream.
On 15th there will be -rc3 which if no release critical bug comes up will be equal to release.
So likely -rc3 will be uploaded this week (before FF) and thereby we meed the deadlines.

I will keep this bug up to date on this.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.5 KiB)

This bug was fixed in the package qemu - 1:2.10~rc3+dfsg-0ubuntu1

---------------
qemu (1:2.10~rc3+dfsg-0ubuntu1) artful; urgency=medium

  * Merge with Debian unstable (2.8) and Upstream 2.10-rci3; This fixes
    a set of bugs
    - [FFE] Qemu 2.10 in Artful (LP: #1699968)
    - CPU hot unplug fails after migrating a CPU hotplugged guest
      from source (LP: #1677552)
    - [Feature] KNL/KNM: Numa Distance on KVM(LP: #1647902)
    - New KVM 288 Pass Through (LP: #1672447)
    - aarch64: MSI is not supported by interrupt controller (LP: #1706630)
  * Remaining changes:
    - qemu-kvm to systemd unit
      - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm,
        hugepages and architecture specifics
      - d/qemu-kvm.service: systemd unit to call qemu-kvm-init
      - d/qemu-system-common.install: install systemd unit and helper script
      - d/qemu-system-common.maintscript: clean old sysv and upstart scripts
      - d/qemu-system-common.qemu-kvm.default: defaults for
        /etc/default/qemu-kvm
      - d/rules: install /etc/default/qemu-kvm
    - Enable nesting by default
      - set nested=1 module option on intel. (is default on amd)
      - re-load kvm_intel.ko if it was loaded without nested=1
      - d/p/ubuntu/expose-vmx_qemu64cpu.patch: expose nested kvm by default
        in qemu64 cpu type.
      - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default
        in qemu64 on amd
    - libvirt/qemu user/group support
      - qemu-system-common.postinst: remove acl placed by udev, and add udevadm
        trigger.
      - qemu-system-common.preinst: add kvm group if needed
    - Distribution specific machine type
      - d/p/ubuntu/define-ubuntu-machine-types.patch: define distro machine
        types to ease future live vm migration.
      - d/qemu-system-x86.NEWS Info on fixed machine type defintions
    - improved dependencies
      - Make qemu-system-common depend on qemu-block-extra
      - Make qemu-utils depend on qemu-block-extra
      - let qemu-utils recommend sharutils
    - s390x support
      - Create qemu-system-s390x package
      - Include s390-ccw.img firmware
      - Enable numa support for s390x
    - ppc64[le] support
      - d/qemu-system-ppc.links provide usr/bin/qemu-system-ppc64le symlink
      - Enable seccomp for ppc64el
      - bump libseccomp-dev dependency, 2.3 is the minimum for ppc64
    - arch aware kvm wrappers
    - disable missing x32 architecture
    - update VCS links
  * Added changes
      - d/rules: or32 is now named or1k (since 4a09d0bb)
      - d/qemu-system-common.docs: new paths since (ac06724a)
      - d/qemu-system-common.install: qmp-commands.txt removed, but replaced
        by qapi-schema.json which is already packaged (since 4d8bb958)
      - Updates in debian/patches to match qemu 2.10
        - d/p/02_kfreebsd.patch: utimensat is no more optional upstream
        - d/p/ubuntu/enable-svm-by-default.patch: target-i386 -> target/i386
        - d/p/ubuntu/expose-vmx_qemu64cpu.patch: target-i386 -> target/i386
        - d/p/ubuntu/define-ubuntu-machine-types.patch: new 2.10 ubuntu types
        - update VCS-git to match the Artful branch
      - s390x pack...

Read more...

Changed in qemu (Ubuntu):
status: Triaged → Fix Released
no longer affects: ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.