Bug 1494181

Summary: Backport vGPU support to qemu-kvm
Product: Red Hat Enterprise Linux 7 Reporter: Martin Tessun <mtessun>
Component: qemu-kvmAssignee: Alex Williamson <alex.williamson>
Status: CLOSED ERRATA QA Contact: Guo, Zhiyi <zhguo>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: chayang, gordon.jin, hang.yuan, jinzhao, jkachuck, juzhang, knoel, michen, mkalinin, mtessun, rbalakri, terrence.xu, virt-maint, zhguo, zhiyuan.lv
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.3-146.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 14:35:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1528122    
Bug Blocks: 1449793, 1461180, 1471872, 1511802, 1522983    

Description Martin Tessun 2017-09-21 15:31:50 UTC 
NVIDIA asked for enabling vGPU support also in RHEL/KVM.
This BZ is for evaluating and tracking this effort.
Comment 6 Miroslav Rezanina 2017-10-24 04:41:09 UTC 
Fix included in qemu-kvm-1.5.3-146.el7
Comment 9 Guo, Zhiyi 2018-01-26 03:27:49 UTC 
QE perform a test run against qemu-kvm-1.5.3-154 and rhel7.5 guest

vgpu type used:
M60-8Q
M60-4Q
M60-2A


https://polarion.engineering.redhat.com/polarion/#/project/RedHatEnterpriseLinux7/testrun?id=virtkvmqe-x86-vgpu-M60-qemu-kvm-1-5-3-154-rhel75

No block issue found during test, one one issue found during use qemu + vgpu + sr-iov, and it has been tracked by Bug 1538866 qemu will coredump after executing info qtree
Comment 10 Guo, Zhiyi 2018-01-26 03:28:49 UTC 
Host/Guest kernel used: 3.10.0-836.el7.x86_64
Host/Guest nvidia vgpu driver used: 390.21
Comment 11 Guo, Zhiyi 2018-01-26 03:29:24 UTC 
Verified per comment 9 & 10
Comment 15 errata-xmlrpc 2018-04-10 14:35:07 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/RHSA-2018:0816