From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Arjen via pve-user <pve-user@lists.proxmox.com>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Enable AES?
Date: Wed, 29 Mar 2023 16:02:28 +0200 [thread overview]
Message-ID: <i0tdfj-c7v.ln1@hermione.lilliput.linux.it> (raw)
In-Reply-To: <mailman.70.1680032963.355.pve-user@lists.proxmox.com>; from SmartGate on Wed, Mar 29, 2023 at 16:06:02PM +0200
Mandi! Arjen via pve-user
In chel di` si favelave...
> Do you use the CPU type host, max or any other type that has aes already included?
No, de default, kvm64.
Where i can find info on different CPU type?!
> If you use kvm64 for example, then you need to enable it in Advanced, Extra CPU Flags.
OK.
> Whether this actually works also depends on pfSense. If it detects a very old CPU type (like 486) then it might not bother to check the aes flag.
/root: grep -i cpu /var/run/dmesg.boot
CPU: Common KVM processor (2095.11-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0: <ACPI CPU> on acpi0
CPU: Common KVM processor (2095.11-MHz K8-class CPU)
/root: sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu'
hw.machine: amd64
hw.model: Common KVM processor
hw.ncpu: 4
hw.machine_arch: amd64
I'll try to enable it and see...
--
Vendere no, non passa tra i miei rischi,
non comprate i miei dischi e sputatemi addosso. (F. Guccini)
prev parent reply other threads:[~2023-03-29 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 17:07 Marco Gaiarin
[not found] ` <mailman.70.1680032963.355.pve-user@lists.proxmox.com>
2023-03-29 14:02 ` Marco Gaiarin [this message]
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=i0tdfj-c7v.ln1@hermione.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.