---
PVE/VZDump.pm | 11 +++
1 file changed, 11 insertions(+)
diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
index 1e00c2d..0280568 100644
--- a/PVE/VZDump.pm
+++ b/PVE/VZDump.pm
@@ -853,6 +853,17 @@ sub exec_backup_task {
# lock VM (prevent config changes)
$plugin->lock_vm ($v
A fresh pve-cluster installation on top of Debian would err
because the ssl private key generation failed.
---
data/PVE/Cluster.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm
index 9e76af3..fa4a08f 100644
--- a/data/PVE/Cluster.pm
+
make code more readable.
---
PVE/QemuMigrate.pm | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 26744f0..ef5d9e6 100644
--- a/PVE/QemuMigrate.pm
+++ b/PVE/QemuMigrate.pm
@@ -287,21 +287,21 @@ sub syn
Offline migration on LVM and LVMThin are possible offline.
---
PVE/QemuMigrate.pm | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 7b9506f..26744f0 100644
--- a/PVE/QemuMigrate.pm
+++ b/PVE/QemuMigrate.pm
@@ -293,12 +
This check ensure that no volume can have snapshots where we are not able to
migrate it.
---
PVE/QemuMigrate.pm | 9 -
PVE/QemuServer.pm | 11 +++
2 files changed, 15 insertions(+), 5 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index ef5d9e6..ce7a5a7 10064
This check ensure that no volume can have snapshots where we are not able to
migrate it.
---
PVE/QemuMigrate.pm | 9 -
PVE/QemuServer.pm | 11 +++
2 files changed, 15 insertions(+), 5 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index ef5d9e6..ddcfa44 10064
Hello,
Any of developers of Proxmox would you please consider checking this forum
post about incremental backup?
https://forum.proxmox.com/threads/why-qemu-incremental-backup-is-not-supported-by-proxmox.2/
Kind Regards
___
pve-devel mailing list
pve
It's possible for two simultaneous VM starts to try to
create vlan bridges on non-vlan-aware bridges
simultaneously, which causes one of them to fail with the
error "can't add bridge ...".
---
As far as I can tell this is the only place reachable via the
pve-bridge script where this can happen.
The
---
pct.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/pct.adoc b/pct.adoc
index 014e48d..9f4fde8 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -243,6 +243,8 @@ ArchLinux:: test /etc/arch-release
Alpine:: test /etc/alpine-release
+Gentoo:: test /etc/gentoo-release
+
NOTE: Container sta
usually, the headers should be installed before the kernel
image, not the other way round, and neither depends on the
other.
---
headers-control.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/headers-control.in b/headers-control.in
index ae8bc33..efccbe2 100644
--- a/header
---
Makefile | 19 ---
proxmox-ve/control-headers | 11 +++
2 files changed, 27 insertions(+), 3 deletions(-)
create mode 100644 proxmox-ve/control-headers
diff --git a/Makefile b/Makefile
index 46312e0..549d16a 100644
--- a/Makefile
+++ b/Makefile
@@ -8
11 matches
Mail list logo