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.

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.

The verification of the Stable Release Update for intel-microcode 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.

I found out a few days ago that release 20140430 fixes one *critical
erratum* for the Xeon E5v2 and Xeon E7v2 processors, as well as a few severe
ones. As per the changelog, other processors did not receive new updates
on this release.

Without the microcode update, any VMs on boxes with Xeon E5v2 and E7v2
processors are at risk of unpredictable behaviour due to incorrect page
translations(!).

That said, these are server platforms, so their users should have received
notice of a EFI/BIOS *critical* firmware update from the server vendor that
includes the microcode update.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh