Bug 1051370 - Filter CPU-Level under cluster policy not work correct
Summary: Filter CPU-Level under cluster policy not work correct
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-10 07:22 UTC by Artyom
Modified: 2016-02-10 20:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-13 12:42:12 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
src_vdsm_log (359.45 KB, text/x-log)
2014-01-10 07:22 UTC, Artyom
no flags Details

Description Artyom 2014-01-10 07:22:32 UTC
Created attachment 848074 [details]
src_vdsm_log

Description of problem:
Have two host with different CPU flags, and cluster policy set to None(include all filters and also CPU-level), migration vm from host with high CPU to low CPU failed with libvirt error:
libvirtError: unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: est.

Version-Release number of selected component (if applicable):
is31

How reproducible:
Always

Steps to Reproduce:
1. Add two hosts with different CPU's, hosts with higher CPU host_high, host with lower host_low
2. Set cluster policy to None, also "Cluster CPU type" set to Intel Conroe Family.
3. Set vm "Allow manual migration only" and check "Use Host CPU"
4. Run vm on host_high and migrate it without specify destination host

Actual results:
Migration Failed and in vdsm log appear libvirt error.

Expected results:
Migration Failed because it not available VDS for migration with error message in engine, because host_low must be filter with CPU-Level filter, and without libvirt error in vdsm.log

Additional info:
host_high with 4 cpu's:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Xeon(R) CPU            5150  @ 2.66GHz
stepping        : 6
cpu MHz         : 2660.122
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dts tpr_shadow
bogomips        : 5320.24
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:


host_low with 2 cpu's:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping        : 6
cpu MHz         : 1999.998
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dts tpr_shadow
bogomips        : 3990.16
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

Comment 1 Itamar Heim 2014-01-10 20:58:45 UTC
that's not a bug if you used -cpu host. doron?

Comment 2 Doron Fediuck 2014-01-12 15:43:19 UTC
Right, we do not support migration using host cpu.
This should actually be blocked, so I suggest you open a bug on it and close this one.

Comment 3 Artyom 2014-01-13 12:42:12 UTC
It's no bug in cluster policies, but bug in migration options, so open new bug https://bugzilla.redhat.com/show_bug.cgi?id=1052168


Note You need to log in before you can comment on or make changes to this bug.