Bug 1288090 - Allow opteron_g2 and newer CPUs for Windows 10 guest OS
Summary: Allow opteron_g2 and newer CPUs for Windows 10 guest OS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-3.5.7
: 3.5.7
Assignee: jniederm
QA Contact: Nisim Simsolo
URL:
Whiteboard: virt
Depends On: 1277214
Blocks: 1269828 1272924
TreeView+ depends on / blocked
 
Reported: 2015-12-03 13:35 UTC by Michal Skrivanek
Modified: 2016-02-10 19:23 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, all AMD Opteron processors were unsupported for Windows 10. With this update, AMD Opteron G2 and newer CPU models are now supported for Windows 10.
Clone Of: 1277214
Environment:
Last Closed: 2016-01-12 20:40:49 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0029 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.5.7 update 2016-01-13 01:39:40 UTC
oVirt gerrit 47979 0 None None None Never
oVirt gerrit 48009 0 None None None Never
oVirt gerrit 49536 0 ovirt-engine-3.5 MERGED core: Opteron G2 and newer allowed for Windows 10 guest OS Never

Description Michal Skrivanek 2015-12-03 13:35:44 UTC 
+++ This bug was initially created as a clone of Bug #1277214 +++

Add support for AMD CPU opteron_g2 and newer for Windows 10 (both 32bit and 64bit) guest OS.

Currently opteron_g1, opteron_g2, opteron_g3, opteron_g4, opteron_g5 AMD CPUs are marked as unsupported for Windows 10.
Comment 1 Nisim Simsolo 2015-12-22 15:43:50 UTC 
Verified using AMD g2 (Dual-Core AMD Opteron(tm) Processor 2212):
rhevm-3.5.7-0.1.el6ev
vdsm-4.16.31-1.el7ev.x86_64
libvirt-client-1.2.17-13.el7_2.2.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.5.x86_64
sanlock-3.2.4-1.el7.x86_64
Comment 4 errata-xmlrpc 2016-01-12 20:40:49 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://rhn.redhat.com/errata/RHBA-2016-0029.html
Note You need to log in before you can comment on or make changes to this bug.