Bug 1117031
| Summary: | [RFE] filter out cluster VM OSs against a black list (e.g. Windows 8.1 on Conroe) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Scott Herold <sherold> |
| Component: | RFEs | Assignee: | Roy Golan <rgolan> |
| Status: | CLOSED ERRATA | QA Contact: | sefi litmanovich <slitmano> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.0 | CC: | aburden, bugs, iheim, istein, lpeer, meverett, michal.skrivanek, pstehlik, rbalakri, rgolan, rpai, wpinheir, yeylon |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature |
| Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-3-6-0-2 | Doc Type: | Enhancement |
| Doc Text: |
Some operating systems are not supported on older CPU architectures. For example, Windows 8 does not run on Conroe-based hosts. When a cluster is set to a certain CPU model, the unsupported operating systems will no longer be available in the 'New Virtual Machine' and 'Edit Virtual Machine' windows for that cluster.
|
Story Points: | --- |
| Clone Of: | 1096851 | Environment: | |
| Last Closed: | 2016-03-09 20:48:42 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: | 1096851 | ||
| Bug Blocks: | |||
|
Description
Scott Herold
2014-07-07 20:46:57 UTC
I got this problem yesterday, using RHEV 3.5.3 Are there any work around to install Windows 8 in hypervisor using this cpu family ?! Appreciate Waldirio Verified on rhevm-3.6.0-0.16.master.el6.noarch according to the polarion test plan. test run: https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/testrun?id=3_6_VIRT_Filter_VM_Os_Against_Cpu_Type_09212015 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/RHEA-2016-0376.html |