Hello,
I noticed that the aes-ni cpuflag isn't exposed to kvm guests.
Is there any specific reason for this or does my kernel has a problem detecting it ?
I'm running version 4.1.3 of the kernel, so it should be recent enough to support it.

Has no one any infos on this ?
I just want to be sure thats not a kernel issue.

Here are the detected flags:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand hypervisor lahf_lm abm fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt

poti, yup seeing same issue with KVM Xeon E5-2680v3 missing aes flag while Xeon E5-2680v3 KVM has the flag and makes all the difference with 2x performance in openssl speed -evp tests see https://community.centminmod.com/posts/17628/

_________________
* Centmin Mod Nginx menu based auto installer (Nginx, PHP-FPM, MariaDB MySQL) :: Centmin Mod LEMP Stack - What's New

poti, Linode is working to enable aes cpu flag on their KVMs.. I just migrated to a Linode KVM with E5-2680v3 and aes enabled https://community.centminmod.com/posts/17850/

Might want to ask Linode support about migrating you to a KVM Linode with aes enabled

_________________
* Centmin Mod Nginx menu based auto installer (Nginx, PHP-FPM, MariaDB MySQL) :: Centmin Mod LEMP Stack - What's New