From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH installer 0/3] export hvm support flag through runtime env
Date: Mon, 3 Jul 2023 09:34:57 +0200 [thread overview]
Message-ID: <20230703073500.290868-1-c.heiss@proxmox.com> (raw)
Currently, the logic to check whether hardware-accelerated
virtualization is supported or not by the host cpu is duplicated.
This adds a `hvm_supported` flag to the runtime environment info,
indicating whether it is supported or not, which can then be used by the
graphical and console installer to display a message to the user as
appropriate.
pve-installer:
Christoph Heiss (3):
run env: add hardware-accelerated virtualization support flag
proxinstall: check hvm support through runtime env info
tui: check hvm support through runtime env info instead of open-coding
Proxmox/Install/RunEnv.pm | 25 +++++++++++++++++++++++++
proxinstall | 13 +++++--------
proxmox-tui-installer/Cargo.toml | 2 --
proxmox-tui-installer/src/main.rs | 25 ++++++++++---------------
proxmox-tui-installer/src/setup.rs | 4 ++++
5 files changed, 44 insertions(+), 25 deletions(-)
--
2.40.1
next reply other threads:[~2023-07-03 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:34 Christoph Heiss [this message]
2023-07-03 7:34 ` [pve-devel] [PATCH installer 1/3] run env: add hardware-accelerated virtualization support flag Christoph Heiss
2023-07-03 7:34 ` [pve-devel] [PATCH installer 2/3] proxinstall: check hvm support through runtime env info Christoph Heiss
2023-07-03 7:35 ` [pve-devel] [PATCH installer 3/3] tui: check hvm support through runtime env info instead of open-coding Christoph Heiss
2023-07-04 8:27 ` [pve-devel] [PATCH installer 4/4] d/control: drop unused librust-proxmox-sys-dev build dependency Christoph Heiss
2023-07-13 13:50 ` [pve-devel] applied-series: [PATCH installer 0/3] export hvm support flag through runtime env 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=20230703073500.290868-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal