[MRE] Xen stable update to 4.2.2

Bug #1180397 reported by Stefan Bader
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xen (Ubuntu)
Fix Released
Low
Stefan Bader
Raring
Fix Released
Low
Stefan Bader

Bug Description

SRU Justification:

Impact: Upstream Xen has released a stable update to 4.2.2. Since Raring and Saucy are based on 4.2 it would be gaining us bug fixes without waiting for people to run into them. Like we do with upstream stable on the kernel.

Fix: Replaced the orig tarballs with the contents of the upstream stable release. Dropping patches we have picked up already.

Testcase: Basic regression testing after upgrading.

MRE discussion: http://irclogs.ubuntu.com/2013/07/22/%23ubuntu-meeting.html#t20:33

Revision history for this message
Stefan Bader (smb) wrote :
Revision history for this message
Stefan Bader (smb) wrote :
Stefan Bader (smb)
description: updated
tags: added: patch
Revision history for this message
James Horner (humankind135) wrote :

Hi There

Would like to see this as upgrading to 13.04/xen 4.2.1 broke pci-e passthrough for me but is fixed in 4.2.2.

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

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

Changed in xen (Ubuntu Raring):
status: New → Confirmed
Revision history for this message
Matthew Alberti (matthewalberti) wrote :

+1. I'm trying to do some PCI passthrough as well.

Revision history for this message
Stefan Bader (smb) wrote :

Actually for Saucy I would rather like to get Xen 4.3 uploaded instead.

Changed in xen (Ubuntu Saucy):
status: In Progress → Won't Fix
Andy Whitcroft (apw)
Changed in xen (Ubuntu Raring):
assignee: nobody → Stefan Bader (smb)
importance: Undecided → Low
status: Confirmed → In Progress
Stefan Bader (smb)
description: updated
Andy Whitcroft (apw)
summary: - Xen stable update to 4.2.2
+ [MRE] Xen stable update to 4.2.2
Revision history for this message
Brian Murray (brian-murray) wrote :

The provisional micro-release exception for Xen includes the following caveat:

Xen, first SRU needs to define a formal regression test procedure, such as "boot the last N releases/LTS default install and verify some list of things (networking, file system test suite, etc.)" (2013-07-22)

Where has that been defined? I do not see it in the description here.

Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Stefan, or anyone else affected,

Accepted xen into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xen/4.2.2-0ubuntu0.13.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in xen (Ubuntu Raring):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in xen (Ubuntu):
status: In Progress → Fix Released
no longer affects: xen (Ubuntu Saucy)
Revision history for this message
Stefan Bader (smb) wrote :

Hi Brian,

not formally yet as I wanted to write that down here as comments with results. Need to see how much effort it will be to leverage some or more of the regression testing that xen upstram does on the git repos. But since I am travelling right now it will get delayed till next week.

Revision history for this message
Stefan Bader (smb) wrote :

Adding the test results as an attachment to keep the formatting sane. Note on the one occasional failure of the security QRT run: one of the tests for /proc/<pid>/maps turns out to be racy at least (I need to talk to the security team about it). But failing or not failing is only depending on execution speed of the test and not a regression at all.

So from my point of view I would hope this to be sufficient regression testing.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xen - 4.2.2-0ubuntu0.13.04.1

---------------
xen (4.2.2-0ubuntu0.13.04.1) raring-proposed; urgency=low

  * Updating to latest upstream stable release (LP: #1180397).
    - Security patches included which replace existing changes:
      * CVE-2012-5634 / XSA-33, CVE-2013-0151 / XSA-34,
        CVE-2013-0152 / XSA-35, CVE-2013-0153 / XSA-36,
        CVE-2013-0215 / XSA-38, CVE-2012-6075 / XSA-41,
        CVE-2013-1917 / XSA-44, CVE-2013-1919 / XSA-46,
        CVE-2013-1920 / XSA-47
    - Additional security related changes, not included before:
      * CVE-2013-0154 / XSA-37: Hypervisor crash due to incorrect ASSERT
                                (debug build only)
      * CVE-2013-1922 / XSA-48: qemu-nbd format-guessing due to missing
                                format specification
    - Bug fixes
      * ACPI APEI/ERST finally working on production systems
      * Bug fixes for other low level system state handling
      * Bug fixes and improvements to the libxl tool stack
      * Bug fixes to nested virtualization
    - Dropping the following patches previously added as they are included
      in the upstream stable release:
      * 0008-vmx-Simplify-cr0-update-handling-by-deferring-cr4-ch.patch
      * 0009-VMX-disable-SMEP-feature-when-guest-is-in-non-paging.patch
      * 0010-VMX-Always-disable-SMEP-when-guest-is-in-non-paging-.patch
 -- Stefan Bader <email address hidden> Tue, 06 Aug 2013 13:26:05 +0100

Changed in xen (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

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.