[pve-devel] superseded: [PATCH storage] api/pvesm: alloc: allow 'vmdk' for the 'format' option

superseded by: https://lore.proxmox.com/pve-devel/20250305104923.23618-1-f.eb...@proxmox.com/T/#m4044c38541bfc2332bbfc0a7930a48ee1d4c3932 Am 07.02.25 um 13:55 schrieb Fiona Ebner: > The API endpoint for allocating an image will automatically detect the > format from the extension for raw, qcow2 an

[pve-devel] applied: [PATCH common v6 1/1] sysfs tools: add 'nvidia' -> 'mdev' workaround to pci_device_info

On 13/02/2025 14:16, Dominik Csapak wrote: > we added it to the lspci one, but we'll also need it when querying > a single device > > code is the same as in the lspci sub > > Signed-off-by: Dominik Csapak > --- > new in v6 > > src/PVE/SysFSTools.pm | 4 > 1 file changed, 4 insertions(+) >

Re: [pve-devel] Strategy for Active Directory and OpenID Connect groups and usernames with spaces and other special characters

> 1. Do we want to allow spaces in groups and/or usernames, or should we > prefer replacement characters (e.g. mapping space(s) to _ or some other > character)? My feeling is that we need to allow all characters - else this will be an endless issue ... > 2. In case we want to allow spaces in