From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Subject: Re: [pve-devel] [PATCH manager 3/3] ui: add 'win11' ostype and set defaults in wizard
Date: Mon, 18 Oct 2021 09:10:23 +0200 [thread overview]
Message-ID: <a05631b5-2910-a0f0-f264-b8aea3b124c2@proxmox.com> (raw)
In-Reply-To: <2244d2ac46c8e62230060e66d374b1f69b1115cf.camel@groupe-cyllene.com>
Hi,
On 18.10.21 07:57, DERUMIER, Alexandre wrote:
> I don't think that win2022 require tpm , only win11.
seems so, but do you think it will hurt if we default to one (in GUI) anyway?
I mean it's only a check box to tick off if one does not wants it.
As otherwise it would add a bit of complication, we'd need to add a separate
win2022 os type just for that.
next prev parent reply other threads:[~2021-10-18 7:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 12:55 [pve-devel] [PATCH 0/3] Windows 11 OS type and UI improvements Stefan Reiter
2021-10-11 12:55 ` [pve-devel] [PATCH qemu-server 1/3] ostype: support Windows 11/Server 2022 Stefan Reiter
2021-10-18 7:54 ` [pve-devel] applied: " Thomas Lamprecht
2021-10-18 8:00 ` Thomas Lamprecht
2021-10-11 12:55 ` [pve-devel] [PATCH manager 2/3] ui: SystemEdit: promote advanced settings to normal Stefan Reiter
2021-10-21 11:51 ` [pve-devel] applied: " Thomas Lamprecht
2021-11-03 13:02 ` Dominik Csapak
2021-11-03 13:26 ` Thomas Lamprecht
2021-10-11 12:55 ` [pve-devel] [PATCH manager 3/3] ui: add 'win11' ostype and set defaults in wizard Stefan Reiter
2021-10-18 5:57 ` DERUMIER, Alexandre
2021-10-18 7:10 ` Thomas Lamprecht [this message]
2021-10-19 9:19 ` DERUMIER, Alexandre
2021-10-21 11:52 ` [pve-devel] applied: " Thomas Lamprecht
2021-10-12 13:51 ` [pve-devel] [PATCH 0/3] Windows 11 OS type and UI improvements Aaron Lauterer
2021-10-12 15:24 ` Thomas Lamprecht
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=a05631b5-2910-a0f0-f264-b8aea3b124c2@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=Alexandre.DERUMIER@groupe-cyllene.com \
--cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox