Hello Jehan, The list of the CPU features required by a VM is defined in its config. In your case the VM created on the source host requires the features that corresponds to Skylake-Client-IBRS. The binding between the architecture names and CPU features is available in /usr/share/libvirt/cpu_map.xml. You can stop the VM and change the CPU model to the one that is supported on the destination. More details on this can be found in https://libvirt.org/formatdomain.html#elementsCPU
> -----Original Message----- > From: users-boun...@openvz.org <users-boun...@openvz.org> On Behalf > Of Vasily Averin > Sent: Friday, September 7, 2018 7:11 PM > To: Jehan PROCACCIA <jehan.procac...@tem-tsp.eu> > Cc: OpenVZ users <users@openvz.org> > Subject: Re: [Users] VM migrate failed Host CPU does not provide required > features: hle, rtm, rdseed... > > Dear Jehan, > > collegians pointed me that cpupools works with vstorage cluster only, and > obviously you are right, it is part of commercial virtuozzo, so it cannot > help in > common case. > > I'm sorry for misinformation. > > Thank you, > Vasily Averin > > On 09/07/2018 05:16 PM, Jehan PROCACCIA wrote: > > unfortunatly I don't have cpupools command available and yum provides > *cpupools gives nothing . > > is it part of commercial virtuozzo support ? I run Virtuozzo Linux > > release 7.5 if that's the case, is there an other way to remove required cpu > feature from the VM and/or host ? > > can I use virt-manager to configure feature or prlct needs to be the only > tool to manipulate the xml representation of the VM ? > > moreover, I read from le guide that the host node needs to be free of all > VM and CT to create a cpupools, which is not easy with my heavy loaded > hosts . > > > > thanks . > > > > ----- Mail original ----- > > De: "Vasily Averin" <v...@virtuozzo.com> > > À: "OpenVZ users" <users@openvz.org>, "Jehan PROCACCIA" > > <jehan.procac...@tem-tsp.eu> > > Envoyé: Vendredi 7 Septembre 2018 14:57:56 > > Objet: Re: [Users] VM migrate failed Host CPU does not provide required > features: hle, rtm, rdseed... > > > > Dear Jahan, > > > > cpopools should help in this situation, it should mask extra CPU > > features and it enables live migration between the nodes. > > https://docs.virtuozzo.com/virtuozzo_7_users_guide/managing-high-avail > > ability-clusters/managing-cpu-pools.html > > > > > > On 09/07/2018 03:45 PM, jehan procaccia TEM-TSP wrote: > > > > > > Hello > > > > when I tried to migrate a VM from on virtuozzo 7 host to an other one > > I get a CPU capabilities not provided by destination > > > > # prlctl migrate myVM root@olympos -v 16 Logging in ... > > security_level=2 > > PrlCleanup::register_hook: 8780700 > > EVENT type=100030 > > Migration started. > > EVENT type=100001 > > EVENT type=100033 > > Operation progress ...98%EVENT type=100033 Operation progress 100% > > EVENT type=100033 Operation progress ... 0%EVENT type=100031 > Migration > > cancelled! > > EVENT type=100007 > > EVENT type=100001 > > > > Failed to migrate the VM: Operation failed. Failed to execute the > > operation. (Details: the CPU is incompatible with host CPU: Host CPU > > does not provide *required features: hle, rtm, rdseed, adx, smap, > > 3dnowprefetch*) > > resultCount: 0 > > PrlCleanup::unregister_hook: 8780700 > > Logging off > > > > indeed those capabilities don't show up in the lshw on the destination > > host (cf PS below ) > > > > alhtough myVM doesn't seem to require those capabilities : > > > > # virsh edit myVM > > ... > > > > <os> > > <type arch='x86_64' machine='pc-i440fx-vz7.7.0'>hvm</type> > > </os> > > <features> > > <acpi/> > > <apic/> > > <pae/> > > <vmcoreinfo state='on'/> > > </features> > > <cpu mode='host-model' check='partial'> <model > > fallback='allow'>Skylake-Client-IBRS</model> > > <topology sockets='1' cores='2' threads='1'/> > > * <feature policy='require' name='ss'/>** > > ** <feature policy='require' name='hypervisor'/>** > > ** <feature policy='require' name='tsc_adjust'/>** > > ** <feature policy='require' name='ssbd'/>** > > ** <feature policy='require' name='stibp'/>** > > ** <feature policy='require' name='pdpe1gb'/>* <feature > > policy='disable' name='arat'/> <feature policy='disable' > > name='xgetbv1'/> <feature policy='disable' name='vmx'/> <feature > > policy='disable' name='xsavec'/> <feature policy='disable' > > name='mpx'/> </cpu> > > > > 1) Is it libvirt or virtuozzo (prlctl) that complains about that ? > > > > 2) how can I tell it to forget about those capabilities ? > > > > 3) should I edit myVM properties with virsh edit or prlct or virt-manager ? > > > > 4) are they all compatible (on can read change done by the other ) ? > > > > Thanks . > > > > PS : CPU hardware capabilities on source host : > > > > # lshw > > description: Rack Mount Chassis > > product: PowerEdge R730 (SKU=NotProvided;ModelName=PowerEdge > R730) > > vendor: Dell Inc. > > serial: 63NXMK2 > > width: 64 bits > > capabilities: smbios-2.8 dmi-2.8 smp vsyscall32 > > *-cpu:0 > > description: CPU > > product: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz > > capabilities: lm fpu fpu_exception wp 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 pdpe1gb rdtscp x86-64 constant_tsc > > arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf > > eagerfpu cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx > > est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic > > movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm > > 3dnowprefetch epb cat_l3 cdp_l3 intel_pt ssbd ibrs ibpb stibp > > tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle > > avx2 smep bmi2 erms invpcid rtm cqm rdt_a *rdseed *adx smap xsaveopt > > cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat > pln > > pts spec_ctrl intel_stibp flush_l1d cpufreq > > configuration: cores=8 enabledcores=8 threads=16 > > > > on destination (rdseed not listed) > > > > # lshw > > description: Rack Mount Chassis > > product: PowerEdge R430 (SKU=NotProvided;ModelName=PowerEdge > R430) > > vendor: Dell Inc. > > serial: DKYSJD2 > > width: 64 bits > > capabilities: smbios-2.8 dmi-2.8 smp vsyscall32 > > *-cpu:0 > > description: CPU > > product: Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz > > vendor: Intel Corp. > > > > capabilities: lm fpu fpu_exception wp 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 pdpe1gb rdtscp x86-64 constant_tsc > > arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf > > eagerfpu cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx > > est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic > > movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm > > epb ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid > > fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt > > cqm_llc cqm_occup_llc dtherm arat pln pts spec_ctrl intel_stibp > > flush_l1d cpufreq > > configuration: cores=6 enabledcores=6 threads=6 > > > > > > > > _______________________________________________ > > Users mailing list > > Users@openvz.org > > https://lists.openvz.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
