Bug 1408230

Summary: Opteron_G4 CPU model broken in QEMU 2.6 with RHEL 6 machine type
Product: [oVirt] vdsm Reporter: Michal Skrivanek <michal.skrivanek>
Component: CoreAssignee: Francesco Romani <fromani>
Status: CLOSED CURRENTRELEASE QA Contact: sefi litmanovich <slitmano>
Severity: high Docs Contact:
Priority: high    
Version: 4.18.4CC: bugs, chayang, dvercill, fromani, jherrman, juzhang, knoel, michal.skrivanek, mkolaja, pbonzini, sbonazzo, sherold, virt-bugs, virt-maint
Target Milestone: ovirt-4.0.7Keywords: Regression
Target Release: ---Flags: rule-engine: ovirt-4.0.z+
rule-engine: blocker+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Using "Opteron" CPU options with Red Hat Enterprise Linux (RHEL) 6 machine types caused the QEMU emulator to terminate unexpectedly due to a typographical error in one of device names. This update corrects the error so "Opteron" CPU options can be used with RHEL 6 machine types as expected.
Story Points: ---
Clone Of: 1408122 Environment:
Last Closed: 2017-02-22 10:31:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1405123, 1408122    
Bug Blocks:    

Description Michal Skrivanek 2016-12-22 14:34:05 UTC
We need to bump up vdsm spec for all branches

+++ This bug was initially created as a clone of Bug #1408122 +++

Comment 1 Red Hat Bugzilla Rules Engine 2016-12-22 14:34:35 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Michal Skrivanek 2016-12-22 15:12:00 UTC
confirmed to affect all rhel-6 based machine types

Comment 3 Sandro Bonazzola 2017-01-24 13:03:34 UTC
Francesco, can you check if qemu-kvm-ev currently in -snapshot is ok so you can move this bug to modified?

Comment 4 Francesco Romani 2017-01-24 13:47:53 UTC
> Francesco, can you check if qemu-kvm-ev currently in -snapshot is ok so you
> can move this bug to modified?

It is:

Fixed in version: qemu-kvm-rhev-2.6.0-28.el7_3.3

http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/el7Server/x86_64/qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64.rpm

but the patch bumping the spec is not yet merged or backported.

Comment 5 Sandro Bonazzola 2017-01-25 07:54:22 UTC
4.0.6 has been the last oVirt 4.0 release, please re-target this bug.

Comment 6 Tomas Jelinek 2017-01-31 16:46:59 UTC
*** Bug 1417944 has been marked as a duplicate of this bug. ***

Comment 7 Francesco Romani 2017-02-01 15:18:03 UTC
nope, still POST

Comment 8 Francesco Romani 2017-02-02 14:06:49 UTC
In branch 4.0.z we still depend on QEMU >= 2.3.0 (https://github.com/oVirt/vdsm/blob/ovirt-4.0/vdsm.spec.in#L256). The Opteron_G4 issue AFAIU affects QEMU 2.6.z, so what to do here? Should we bump the dep to >= 2.6.0 also on branch 4.0.z?

Comment 9 Francesco Romani 2017-02-06 15:37:09 UTC
(In reply to Francesco Romani from comment #8)
> In branch 4.0.z we still depend on QEMU >= 2.3.0
> (https://github.com/oVirt/vdsm/blob/ovirt-4.0/vdsm.spec.in#L256). The
> Opteron_G4 issue AFAIU affects QEMU 2.6.z, so what to do here? Should we
> bump the dep to >= 2.6.0 also on branch 4.0.z?

I can answer myself.
The regression was introduced during one 2.6 rebase, it is not present in the 2.3.0 codebase.
Thus, the only vulnerability in the 4.0.z branch is on RHEL7.3, and only if one user manages to update to the buggy version of qemu, but this will be automatically fixed when yum -y update is run again.

Thus, we don't need patches to 4.0.z branch.

THe patch was merged on master and ovirt-4.1 branch, so we can move to MODIFIED.

Comment 10 Michal Skrivanek 2017-02-22 10:31:38 UTC
fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1408122#c9