Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1582483

Summary:	Running VMs with IBRS CPU fail to migrate after adding SSBD CPUs
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	ovirt-engine	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED ERRATA	QA Contact:	Israel Pinto <ipinto>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.2.3	CC:	lsurette, rbalakri, Rhev-m-bugs, rik.theys, srevivo, trichard, ykaul
Target Milestone:	ovirt-4.2.3-1	Keywords:	Rebase, Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:	This release fixes a regression from a previous update that caused a live migration of a virtual machine using one of the IBRS CPU types to fail.	Story Points:	---
Clone Of:
Clones:	1582490 (view as bug list)		Environment:
Last Closed:	2018-05-29 12:05:01 UTC	Type:	Bug
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:
Bug Blocks:	1582490

Description Michal Skrivanek 2018-05-25 11:44:05 UTC

CPU-Level filter of the default scheduling policy breaks after the recent update which added SSBD variants of CPUs. Because the code was changed to use libvirt CPU flags directly it fails on comparing that with what the VM was started with.

This affects all running VMs using -IBRS CPU Type which were started before this update (<4.2.3.6).

WA is to copy the current scheduling policy, edit, remove CPU-Level filter and set it for the affected Cluster. Host being Operational provides enough safety for migration.

Comment 1 Sandro Bonazzola 2018-05-25 12:47:04 UTC

Originally reported by Rik Theys (rtheys) on #ovirt IRC channel on May 25th 2018

Comment 3 Israel Pinto 2018-05-29 11:25:50 UTC

Steps:
On old version: 
1. Install 2 host with IBRS CPU 
2. Start VM on one host
3. Check CPU model on VM  
UI: Guest CPU Type:SandyBridge-IBRS
From VM: cat /proc/cpuinfo:
         model name	: Intel Xeon E312xx (Sandy Bridge, IBRS update)

4. Upgrade to: 4.2.3-6
Failed to migrate / maintenance host - fail on filter CPU-Level
Enigne log: 
2018-05-29 10:07:11,066+03 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-36) [17ab67d3] Candidate host 'host_11' ('511638be-5325-4955-9124-3330e5a29e77') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'CPU-Level' (correlation id: null)
2018-05-29 10:07:11,066+03 WARN  [org.ovirt.engine.core.bll.MigrateVmCommand] (default task-36) [17ab67d3] Validation of action 'MigrateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__MIGRATE,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName host_11,$filterName CPU-Level,SCHEDULING_HOST_FILTERED_REASON
2018-05-29 10:07:11,068+03 INFO  [org.ovirt.engine.core.bll.MigrateVmCommand] (default task-36) [17ab67d3] Lock freed to object 'EngineLock:{exclusiveLocks='[4626c8d8-9322-4fda-950e-8d8b1db6d846=VM]', sharedLocks=''}'
2018-05-29 10:07:11,090+03 ERROR [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (default task-36) [17ab67d3] Failed to migrate VM 'test_cluster'

5. Upgrade to: aysnc 4.2.3.10 (ovirt-engine-4.2.3.8-0.1)
 1. Running VM:
    Migrate - PASS
    Maintenance host -PASS
 2. New VM 
    CPU type update to: XXX,+spec-ctrl
    Migrate - PASS
    Maintenance host - PASS

Comment 6 errata-xmlrpc 2018-05-29 12:05:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1746

Comment 7 Franta Kust 2019-05-16 13:05:47 UTC

BZ<2>Jira Resync