From: "JR Richardson" <jmr.richardson@gmail.com>
To: "'?????? ???????'" <tsabolov@t8.ru>,
"'Proxmox VE user list'" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] CPU Flag AES-NI Not Offered in CPU Flags [SOLVED]
Date: Tue, 22 Mar 2022 06:30:59 -0500 [thread overview]
Message-ID: <000601d83de0$4e685a60$eb390f20$@gmail.com> (raw)
Yep, that did it, even though aes-ni is not defined in the cpu flags, the VM has access and can use the EVP instruction set, we are good to go.
Thanks!
JR
Hi,
Check this page
https://www.cyberciti.biz/faq/how-to-find-out-aes-ni-advanced-encryption-enabled-on-linux-system/
And try the commands.
21.03.2022 20:50, JR Richardson пишет:
Hi Folks,
I'm running:
CPU(s)
40 x Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (2 Sockets)
Kernel Version
Linux 5.4.174-2-pve #1 SMP PVE 5.4.174-2 (Thu, 10 Mar 2022 15:58:44 +0100)
PVE Manager Version
pve-manager/6.4-14/15e2bf61
This is on a Dell PE R630, BIOS reported AES-NI Enabled.but when I
check /proc/cpuinfo the only flag is 'aes', I don't have 'aes-ni',
what am I missing?
Thanks. Regards
JR
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com <mailto:pve-user@lists.proxmox.com>
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
С уважением
Сергей Цаболов
Системный Администратор ООО "Т8"
Тел.: +74992716161
Моб: +79850334875
<https://t8.ru>
tsabolov@t8.ru <mailto:tsabolov@t8.ru>
ООО «Т8», 107076, г. Москва
Краснобогатырская ул., д. 44, стр.1
www.t8.ru <https://t8.ru/>
reply other threads:[~2022-03-22 11:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000601d83de0$4e685a60$eb390f20$@gmail.com' \
--to=jmr.richardson@gmail.com \
--cc=pve-user@lists.proxmox.com \
--cc=tsabolov@t8.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox