Proxmox CPU model kvm64 with PCID and AES flags

[Leith Hobson]

is this on latest pve 5.2 and only from manual editing the vm conf?

Yes, exactly

That said, I ran some benchmarks quickly for you.
I'm not sure if it's related to my host (E3 1225 V5) but the AES performance is about 4-5 times better WITHOUT the aes tag. So, I'm removing it from my VM.

Perhaps something has been built in?

 

[chrone]

Yes, exactly

That said, I ran some benchmarks quickly for you.
I'm not sure if it's related to my host (E3 1225 V5) but the AES performance is about 4-5 times better WITHOUT the aes tag. So, I'm removing it from my VM.

Perhaps something has been built in?

Awesome, thanks for testing.

Does the default kvm64 cpu type AES performance the same as host cpu type as well? I noticed there's a good amount of reduction in the cpu utilization on nginx load balancer VM when using cpy type host compared with kvm64.

 

[Leith Hobson]

Awesome, thanks for testing.

Does the default kvm64 cpu type AES performance the same as host cpu type as well? I noticed there's a good amount of reduction in the cpu utilization on nginx load balancer VM when using cpy type host compared with kvm64.

That is unfortunately not something that I can answer accurately.

The main issue with host is that it can cause issues with migration

 

[Amin Vakil]

Wrote a small patch that you can add aes, avx, avx2 to the vmconfig file and enable these for your guest.

If someone like the *deb for testing or other cpu-flags feel free to ask.

How did you add avx and avx2 flag to vmconfig file?