Bug 1537032
Summary: | [RFE] Skylake-server support | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Michal Skrivanek <michal.skrivanek> |
Component: | rhevm-setup-plugins | Assignee: | Michal Skrivanek <michal.skrivanek> |
Status: | CLOSED ERRATA | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | bgraveno, bugs, lsurette, mavital, mtessun, rbalakri, Rhev-m-bugs, smaudet, srevivo, ykaul |
Target Milestone: | ovirt-4.2.2 | Keywords: | FutureFeature |
Target Release: | --- | Flags: | mavital:
testing_plan_complete+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhvm-setup-plugins-4.2.2-1.el7ev | Doc Type: | Enhancement |
Doc Text: |
Skylake Server CPU family is now supported by Red Hat Virtualization.
Note: The previous "Skylake" family has been renamed to "Skylake Client" to differentiate.
|
Story Points: | --- |
Clone Of: | 1517286 | Environment: | |
Last Closed: | 2018-05-15 17:33:21 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: | 1501508, 1517286 | ||
Bug Blocks: | 1560792 |
Description
Michal Skrivanek
2018-01-22 10:13:02 UTC
change merged to rhvm-setup-plugins master Verified with: Engine Version:4.2.2.4-0.1.el7 Host: OS Version:RHEL - 7.5 - 8.el7 VDSM Version:vdsm-4.20.20-1.el7ev Kernel Version:3.10.0 - 861.el7.x86_64 KVM Version:2.10.0 - 21.el7_5.1 LIBVIRT Version:libvirt-3.9.0-14.el7 Host info: # virsh -r capabilities | head <capabilities> <host> <uuid>965ad785-91c5-4d4c-8f4a-fd299017ba2c</uuid> <cpu> <arch>x86_64</arch> <model>Skylake-Server</model> <vendor>Intel</vendor> <microcode version='33554485'/> <topology sockets='1' cores='26' threads='2'/> Verification steps: 1.Add Host1 2.Run VM1 on Host1 3.VM1 up and running 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/RHEA-2018:1473 BZ<2>Jira Resync |