Red Hat Bugzilla – Bug 1275810
VM can be started with incompatible CPU and guest OS
Last modified: 2016-02-10 14:24:07 EST
Description of problem:
VM can be started even if the current cluster cpu is compatible with selected guest OS (as defined in osinfo-defaults.properties).
Version-Release number of selected component (if applicable):
3.6, commit bd5ce0c
Steps to Reproduce:
1. Make sure, cluster CPU is newer than Conroe
2. Create VM with Windows 10 guest OS
3. Change Cluster CPU to Conroe
4. Start the VM
The VM starts.
Error message regarding incompatible CPU and guest OS should be shown.
This relates to https://bugzilla.redhat.com/show_bug.cgi?id=1269828
Verified on rhevm 184.108.40.206-0.1.el6
When trying to run win 10 VM on Intel host, that it's cluster changed from sunday bridge to conroe, the VM failed to start:
Operation failed window opened, with this message:
"Error while executing action:
The guest OS doesn't support the following CPUs: opteron_g1, conroe, nehalem, penryn. Its possible to change the cluster cpu or set a different one per VM"
Changing cluster to westmere -> vm started OK.
I'd recommend, to add this message the supported cpu is westmare+, so it would be more clear what cpus are supported.
oVirt 3.6.1 has been released and bz verified, moving to closed current release