[pve-devel] applied: [PATCH manager 1/1] CPU flags: Add aes flag

Thomas Lamprecht t.lamprecht at proxmox.com
Fri Aug 23 10:43:01 CEST 2019


On 01.08.19 19:39, Peter Keresztes Schmidt wrote:
> Signed-off-by: Peter Keresztes Schmidt <peterke at sos.ethz.ch>
> ---
>  www/manager6/form/VMCPUFlagSelector.js | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/www/manager6/form/VMCPUFlagSelector.js b/www/manager6/form/VMCPUFlagSelector.js
> index 2612be11..dec9de54 100644
> --- a/www/manager6/form/VMCPUFlagSelector.js
> +++ b/www/manager6/form/VMCPUFlagSelector.js
> @@ -32,7 +32,8 @@ Ext.define('PVE.form.VMCPUFlagSelector', {
>  	    { flag: 'amd-no-ssb', desc: 'Notifies guest OS that host is not vulnerable for Spectre on AMD CPUs' },
>  	    { flag: 'pdpe1gb', desc: 'Allow guest OS to use 1GB size pages, if host HW supports it' },
>  	    { flag: 'hv-tlbflush', desc: 'Improve performance in overcommitted Windows guests. May lead to guest bluescreens on old CPUs.' },
> -	    { flag: 'hv-evmcs', desc: 'Improve performance for nested virtualization. Only supported on Intel CPUs.' }
> +	    { flag: 'hv-evmcs', desc: 'Improve performance for nested virtualization. Only supported on Intel CPUs.' },
> +	    { flag: 'aes', desc: 'Activate AES instruction set for HW acceleration.' }
>  	],
>  	listeners: {
>  	    update: function() {
> 

applied, thanks!



More information about the pve-devel mailing list