[pve-devel] [PATCH proxmox-i18n] ja: Improve translation

2024-01-24 Thread ribbon
I have reviewed the whole Japanese translation. ___ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH http-server] access control: avoid "uninitialized value" warning if using IP ranges

2024-01-24 Thread Friedrich Weber
ALLOW_FROM/DENY_FROM accept any syntax understood by Net::IP. However, if an IP range like "10.1.1.1-10.1.1.3" is configured, a confusing Perl warning is printed to the syslog on a match: Use of uninitialized value in concatenation (.) or string at [...] The reason is that we use Net::IP::prefi

Re: [pve-devel] [PATCH installer 0/6] switch low-level installer protocol to json

2024-01-24 Thread Christoph Heiss
Ping. As this is a prerequisite for the auto-installer [0], it would be nice to get this is sooner than later. [0] https://lists.proxmox.com/pipermail/pve-devel/2024-January/061431.html On Wed, Dec 06, 2023 at 12:34:49PM +0100, Christoph Heiss wrote: > > This switches the stdio-protocol for th

Re: [pve-devel] [PATCH installer 0/2] expose zfs arc size setting for all products

2024-01-24 Thread Christoph Heiss
Ping. On Thu, Nov 30, 2023 at 11:01:41AM +0100, Christoph Heiss wrote: > > As suggested by Thomas, sets the default to 50% for all non-PVE > products. > > Quickly smoke-tested this, to see if all installer show the correct > value in the GUI/TUI. > > Christoph Heiss (2): > tui: expose arc size

[pve-devel] [PATCH qemu-server v8 1/4] machine as property-string

2024-01-24 Thread Markus Frank
Convert the machine parameter to a property-string and use the machine type as the default key for backward compatibility. Signed-off-by: Markus Frank --- PVE/API2/Qemu.pm | 9 +++-- PVE/QemuConfig.pm | 3 ++- PVE/QemuServer.pm | 16 ++- PVE/QemuServer/

[pve-devel] [PATCH qemu-server v8 2/4] fix #3784: Parameter for guest vIOMMU + test-cases

2024-01-24 Thread Markus Frank
vIOMMU is the emulation of a hardware IOMMU within a virtual machine, providing improved memory access control and security for virtualized I/O devices. vIOMMU also enables the option to passthrough pci devices to L2 VMs in L1 VMs via Nested Virtualisation. Currently there are two vIOMMU implemen

[pve-devel] [PATCH manager v8 4/4] ui: MachineEdit with viommu ComboBox

2024-01-24 Thread Markus Frank
Added a proxmoxKVComboBox for selecting a vIOMMU implementation for a VM. If i440fx is selected, a hint tells that q35 is required for Intel vIOMMU. The UI also needs to parse the new machine parameter as PropertyString. Signed-off-by: Markus Frank --- www/manager6/qemu/MachineEdit.js | 45

[pve-devel] [PATCH qemu-server/docs/manager v8 0/4] vIOMMU-Feature #3784

2024-01-24 Thread Markus Frank
overall change in v8: * rebase to master I was able to clarify any ambiguity regarding vIOMMU: https://lists.gnu.org/archive/html/qemu-devel/2023-10/msg02370.html The iommu_platform parameter could be made an optional parameter for VirtIO devices to add more isolation (with the downside of making

[pve-devel] [PATCH docs v8 3/4] added vIOMMU documentation

2024-01-24 Thread Markus Frank
Signed-off-by: Markus Frank --- qm-pci-passthrough.adoc | 51 + qm.adoc | 1 + 2 files changed, 52 insertions(+) diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc index 3abeb50..04a3bc2 100644 --- a/qm-pci-passthrough.adoc +++

[pve-devel] [PATCH proxmox-i18n] ja: Improve translation

2024-01-24 Thread ribbon
I have reviewed the whole Japanese translation. ___ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel