FFE: create a trusty machine type

Bug #1294823 reported by Serge Hallyn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
High
Unassigned
qemu (Ubuntu)
Fix Released
High
Unassigned

Bug Description

We should create a new machine type, perhaps 'trusty', aliased to the newest qemu machine type. This should help us to ensure the feasability of lts-to-lts migrations from trusty to next lts.

CVE References

Changed in qemu (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

We should also consider making the new machine type a default in libvirt.

Changed in libvirt (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

The newest 2.0 candidate qemu at ppa:ubuntu-virt/candidate now has a patch to define the trusty machine type and make it default. Since this by itself would break libvirt, the ppa now also has a libvirt package recognizing 'trusty' as a i440fx machine type.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hi - I notice that this hasn't yet gotten an ack/nack from the release team.

Ping?

Revision history for this message
Stéphane Graber (stgraber) wrote :

Sounds like something useful to me, granted.

Revision history for this message
Stéphane Graber (stgraber) wrote :

FFe bugs must be in new/confirmed for the release team to look at them, the Triaged status is for approved FFes.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.2.2-0ubuntu10

---------------
libvirt (1.2.2-0ubuntu10) trusty; urgency=medium

  * d/p/recognize-trusty-machine-type.patch: handle "trusty" qemu machine type
    (LP: #1294823)
 -- Serge Hallyn <email address hidden> Fri, 04 Apr 2014 09:29:22 -0500

Changed in libvirt (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qemu - 2.0.0~rc1+dfsg-0ubuntu1

---------------
qemu (2.0.0~rc1+dfsg-0ubuntu1) trusty; urgency=medium

  * Merge 2.0.0-rc1
  * debian/rules: consolidate ppc filter entries.
  * Move qemu-system-arch64 into qemu-system-arm
  * debian/patches/define-trusty-machine-type.patch: define a trusty machine
    type, currently the same as pc-i440fx-2.0, to put is in a better position
    to enable live migrations from trusty onward. (LP: #1294823)
  * debian/control: build-dep on libfdt >= 1.4.0 (LP: #1295072)
  * Merge latest upstream git to commit dc9528f
  * Debian/rules:
    - remove -enable-uname-release=2.6.32
    - don't make the aarch64 target Ubuntu-specific.
  * Remove patches which are now upstream:
    - fix-smb-security-share.patch
    - slirp-smb-redirect-port-445-too.patch
    - linux-user-Implement-sendmmsg-syscall.patch (better version is upstream)
    - signal-added-a-wrapper-for-sigprocmask-function.patch
    - ubuntu/signal-sigsegv-protection-on-do_sigprocmask.patch
    - ubuntu/Don-t-block-SIGSEGV-at-more-places.patch
    - ubuntu/ppc-force-cpu-threads-count-to-be-power-of-2.patch
  * add link for /usr/share/qemu/bios-256k.bin
  * Remove all linaro patches.
  * Remove all arm64/ patches. Many but not all are upstream.
  * Remove CVE-2013-4377.patch which is upstream.
  * debian/control-in: don't make qemu-system-aarch64 ubuntu-specific
 -- Serge Hallyn <email address hidden> Tue, 25 Feb 2014 22:31:43 -0600

Changed in qemu (Ubuntu):
status: Triaged → Fix Released
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.