[Users] Xeon 5060 support "Dempsey"

[Itamar Heim]

On 02/02/2014 12:36 AM, Peter Galgano wrote:
>
> Thanks for your help with the config change, Itamar
>
> So am I correct that the config change is to be made in the
> serverCPUList setting?

yes.

>
> May I please request the proper format of the configuration lines, and
> clear documentation of how to apply this workaround?

i went to 3.0 tag in the git repo.

it was:
select fn_db_add_config_value('ServerCPUList','2:Intel Xeon w/o 
XD/NX:vmx,sse2:qemu64,-nx,+sse2; 3:Intel Xeon:vmx,sse2,nx:qemu64,+sse2; 
4:Intel Conroe Family:vmx,sse2,nx,cx16,ssse3:qemu64,+sse2,+cx16,+ssse3; 
5:Intel Penryn 
Family:vmx,sse2,nx,cx16,ssse3,sse4_1:qemu64,+sse2,+cx16,+ssse3,+sse4.1; 
6:Intel Nehalem 
Family:vmx,sse2,nx,cx16,ssse3,sse4_1,sse4_2,popcnt:qemu64,+sse2,+cx16,+ssse3,+sse4.1,+sse4.2,+popcnt; 
2:AMD Opteron G1 w/o NX:svm,sse2:qemu64,-nx,+sse2; 3:AMD Opteron 
G1:svm,sse2,nx:qemu64,+sse2; 4:AMD Opteron 
G2:svm,sse2,nx,cx16:qemu64,+sse2,+cx16; 5:AMD Opteron 
G3:svm,sse2,nx,cx16,sse4a,misalignsse,popcnt,abm:qemu64,+sse2,+cx16,+sse4a,+misalignsse,+popcnt,+abm;','2.2');

I think this would work for you (check you have sse2 today via cat 
/proc/cpuinfo | grep sse2)
3:Intel Xeon:vmx,sse2,nx:qemu64,+sse2
(change the number from 3 to something which doesn't exist in the 
current ServerCPUList you have.

format is:
3 - sort/id
Intel Xeon - display name
vmx,sse2,nx - flags engine verifies appear in getVdsCaps for this host
qemu64,+sse2 - the cpu/flags engine passes to vdsm to pass to libvirt/qemu


>
> Perhaps we can collect our older processors into some "other" supported
> but not "known or proper or whatever" models. Your system can give us a
> warning for attempting an unexpected processor, but hosts are allowed to
> run. Isn't it obvious that an older processor may provide lesser
> capability compared to a newer one?
>
> I'm installing on this hardware to gain experience with ovirt. and put a
> lab server together to test a roadmap to HA. I understand that i may not
> be the targeted audience, and you may not support all hardware..
>
> Respectfully to the developers, in my opinion I don't have an arbitrary
> set of cpu flags, I have two xeon 5060 "dempsey" processors which have
> been visualization workhorses for years. They are well known have a
> standard set of "flags" happily run about every known operating system
> and visualization environment except Ovirt at this point. Having
> stumbled on this limitation, and having spent hours trying to figure it
> out, it could be considered arbitrary that my processor didn't work
> without warning. Respectfully I think think it is most appropriate that
> the system allows my processor to run hosts and if it is not supported
> the system should provide a helpful message that provides some hope of
> being able to google a workaround or whatever.

actually, i wonder which flag its missing that libvirt did not detect it 
as any supported model.