Signed-off-by: Aaron Lauterer
---
similar as in
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=b380cb5814ec551588dfcbd6c5ed190f01d54029
src/window/AddTfaRecovery.js | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/window/AddTfaRecovery.js b/src/window/AddTfaRecovery.js
index 17
Looks like a python-cryptography maintainer opened a pull request on
Github with the exact same change:
https://github.com/proxmox/pve-common/pull/8
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/list
As described in:
https://qemu-project.gitlab.io/qemu/about/removed-features.html#chardev-backend-aliases-tty-and-parport-removed-in-8-0
Signed-off-by: Fiona Ebner
---
PVE/QemuServer.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
i
like the deprecation message printed by QEMU suggests.
Signed-off-by: Fiona Ebner
---
PVE/QemuServer.pm | 2 +-
test/cfg2cmd/custom-cpu-model-host-phys-bits.conf.cmd | 3 +--
test/cfg2cmd/custom-cpu-model.conf.cmd | 3
Fiona Ebner (4):
cfg2cmd: use actual backend names instead of removed tty and paraport
aliases
cfg2cmd: replace deprecated no-acpi option with acpi=off machine flag
cfg2cmd: replace deprecated no-hpet option with hpet=off machine flag
schema: avoid using deprecated -no-hpet in example f
instead use a recent example that served as a workaround in #4625.
Signed-off-by: Fiona Ebner
---
PVE/QemuServer.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index ed7e3f67..9175e4cb 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServ
like the deprecation message printed by QEMU suggests.
Signed-off-by: Fiona Ebner
---
PVE/QemuServer.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index c7caa163..ffef9321 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -38
The pve_verify_cidr{,v4,v6} functions were originally intended for
the /etc/network/interfaces API endpoints and thus are a bit
restrictive. For example, as reported in the community forum[0],
pve_verify_cidr() does not consider '0::/0' and '0::/1' to be valid.
The error message in this scenario b