From: "Сергей Цаболов" <tsabolov@t8.ru>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
JR Richardson <jmr.richardson@gmail.com>
Subject: Re: [PVE-User] CPU Flag AES-NI Not Offered in CPU Flags
Date: Tue, 22 Mar 2022 10:24:13 +0300 [thread overview]
Message-ID: <d1074d34-e723-9817-55c8-bdc034b7a6b7@t8.ru> (raw)
In-Reply-To: <CA+U74VP7iCLDt74k_J7egg_vTLDsE6h4+JQQONSm5R=8En-FJg@mail.gmail.com>
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
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
С уважением
Сергей Цаболов
Системный Администратор ООО "Т8"
Тел.: +74992716161
Моб: +79850334875
logo_T8rus <https://t8.ru>
tsabolov@t8.ru
ООО «Т8», 107076, г. Москва
Краснобогатырская ул., д. 44, стр.1
www.t8.ru <https://t8.ru/>
From d.csapak@proxmox.com Tue Mar 22 09:40:26 2022
Return-Path: <d.csapak@proxmox.com>
X-Original-To: pve-user@lists.proxmox.com
Delivered-To: pve-user@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id 7F16668E59
for <pve-user@lists.proxmox.com>; Tue, 22 Mar 2022 09:40:26 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 6AFE11B486
for <pve-user@lists.proxmox.com>; Tue, 22 Mar 2022 09:39:56 +0100 (CET)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
[94.136.29.106])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by firstgate.proxmox.com (Proxmox) with ESMTPS id E7B1B1B47B
for <pve-user@lists.proxmox.com>; Tue, 22 Mar 2022 09:39:55 +0100 (CET)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
by proxmox-new.maurer-it.com (Proxmox) with ESMTP id AEE3746EC7;
Tue, 22 Mar 2022 09:33:54 +0100 (CET)
Message-ID: <6ff59975-2119-d189-d28b-03ae53033f17@proxmox.com>
Date: Tue, 22 Mar 2022 09:33:53 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:99.0) Gecko/20100101
Thunderbird/99.0
Content-Language: en-US
To: Fabrizio Cuseo <f.cuseo@panservice.it>,
Proxmox VE user list <pve-user@lists.proxmox.com>
References: <976805195.158838.1647854019656.JavaMail.zimbra@zimbra.panservice.it>
From: Dominik Csapak <d.csapak@proxmox.com>
In-Reply-To: <976805195.158838.1647854019656.JavaMail.zimbra@zimbra.panservice.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.001 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
NICE_REPLY_A -0.001 Looks like a legit reply (A)
POISEN_SPAM_PILL 0.1 Meta: its spam
POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes
POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
T_SCC_BODY_TEXT_LINE -0.01 -
Subject: Re: [PVE-User] Extract a single backup from PBS
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 08:40:26 -0000
On 3/21/22 10:13, Fabrizio Cuseo wrote:
> Good morning.
>
> I would like to have a cli command to extract the last (or selected) backup from PBS, saving it in RAW or QCOW2, to be able to download for archiving purpose.
> There is already an option to do it ?
>
> Thank you, Fabrizio
>
Hi,
that should be
proxmox-backup-client restore <type>/<group>/<snapshot-id> <archive-name> <target-path>
<remaining-options>
for example:
proxmox-backup-client restore vm/100/2022-01-01T01:01:01Z drive-scsi0.img /target/scsi0.raw
--repository ...
see 'man proxmox-backup-client' for more details
hope this helps
kind regards
Dominik
prev parent reply other threads:[~2022-03-22 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:50 JR Richardson
2022-03-22 7:24 ` Сергей Цаболов [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=d1074d34-e723-9817-55c8-bdc034b7a6b7@t8.ru \
--to=tsabolov@t8.ru \
--cc=jmr.richardson@gmail.com \
--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.