search for: cpuid_mask_ecx

Displaying 4 results from an estimated 4 matches for "cpuid_mask_ecx".

2013 Jun 25
6
Heterogeneous XCP 1.6 pool
Hi, I''ve been trying to use E5520 and X5650 together in an heterogeneous pool without success. I know the combination is not on the official XenServer supported list (http://hcl.xensource.com/CPUPoolsList.aspx), but I thought it would be possible to set the mask anyway and see for myself if the combination works… My problem is that the mask doesn''t "stick" after a
2008 Jul 09
3
[PATCH]: Add support for Intel CPUID Feature mask in Xen
...ID.1.EAX >= 0x00010674) support cupid mask features. Cpuid feature mask is used to limit the feature flags reported by CPUID.1.EDX:ECX. This small patch adds CPUID feature mask support in XEN by adding boot options in Grub entry as below example: kernel /boot/xen.gz com1=115200,8n1 console=com1 cpuid_mask_ecx = 0xFFFF7FFF cpuid_mask_edx = 0xFFFFFFFC For detailed usage information, please refer to the attached document: cupid_feature_mask.txt. Thanks& Regards, Criping _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/x...
2012 Jan 09
0
Bug#649141: closed by Bastian Blank <waldi@debian.org> (no bug)
...et CPU feature mask on CPU#10 (XEN) Cannot set CPU feature mask on CPU#11 (XEN) Cannot set CPU feature mask on CPU#12 (XEN) Cannot set CPU feature mask on CPU#13 (XEN) Cannot set CPU feature mask on CPU#14 (XEN) Cannot set CPU feature mask on CPU#15 when trying to boot with the following options: cpuid_mask_ecx=0x0008E3FD cpuid_mask_edx=0xBFEBFBFF It accepts and tries to act on the mask, but does not succeed. Also does not give indication as to why. -- Marcus Furlong
2014 Aug 26
1
Masking CPU flags via libvirt xml not working?
Hi, Has anyone here managed to get cpu masking working via libvirt? Intention to enable VM migrations between hosts of a different CPU generation. Inside my xml I'm providing the model as well as a list of features to specifically disable, but none of it seems to take any effect. On booting the VM I still see the disabled flags in /proc/cpuinfo <cpu match='exact'