From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] pve6to7: add check for 'lxc.cgroup.' keys in container config
Date: Wed, 7 Jul 2021 12:46:16 +0200 [thread overview]
Message-ID: <071aa293-69d7-a85a-21e5-af2b567919e4@proxmox.com> (raw)
In-Reply-To: <20210707084419.2264646-1-s.ivanov@proxmox.com>
On 07.07.21 10:44, Stoiko Ivanov wrote:
> The check is rather straight forward - and might help users who
> passthrough devices to their containers.
>
> Reported in our community forum:
> https://forum.proxmox.com/threads/pve-7-0-lxc-intel-quick-sync-passtrough-not-working-anymore.92025/
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> Tested quickly by pasting the lxc.cgroup.devices keys from the thread into a
> container config.
>
> PVE/CLI/pve6to7.pm | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
>
applied, thanks!
But I merged it into the (now renamed) note length check to avoid iterating and parsing
all CT config multiple times.
prev parent reply other threads:[~2021-07-07 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 8:44 [pve-devel] " Stoiko Ivanov
2021-07-07 10:46 ` Thomas Lamprecht [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=071aa293-69d7-a85a-21e5-af2b567919e4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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