---
src/PVE/INotify.pm | 53 +++--
1 file changed, 51 insertions(+), 2 deletions(-)
diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm
index 2c1af3c..2401ec0 100644
--- a/src/PVE/INotify.pm
+++ b/src/PVE/INotify.pm
@@ -898,7 +898,9 @@ sub __read_e
---
src/PVE/INotify.pm | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm
index 0b9ea4a..25ab868 100644
--- a/src/PVE/INotify.pm
+++ b/src/PVE/INotify.pm
@@ -875,6 +875,8 @@ sub __read_etc_network_interfaces {
if ((
---
src/PVE/INotify.pm | 54 +-
1 file changed, 53 insertions(+), 1 deletion(-)
diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm
index 25ab868..2c1af3c 100644
--- a/src/PVE/INotify.pm
+++ b/src/PVE/INotify.pm
@@ -916,6 +916,11 @@ sub __read_
This patches serie add support for new interfaces and options:
- mtu : for ifupdown && ifupdown2
- vxlan interfaces for ifupdown2
- bridgeports options for ifupdown2
Alexandre Derumier (3):
Inotify: add mtu support
Inotify : add vxlan interface support
Inotify : add bridge ports options
Users have reported cpu problem with last windows 10 update (1803)
https://forum.proxmox.com/threads/high-cpu-load-for-windows-10-guests-when-idle.44531/
adding hyperv hv_stimer && hv_synic fix the problem.
This patch series add support to defines them as cpu options,
and enable them by default
---
PVE/QemuServer.pm | 5 +
1 file changed, 5 insertions(+)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 1e4ac5d..6a355f8 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -6597,6 +6597,11 @@ sub add_hyperv_enlightenments {
if ($winversion >= 7) {
push @$cpuF
---
PVE/QemuServer.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index d6efb3a..1e4ac5d 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -155,7 +155,7 @@ my $cpu_vendor_list = {
max => 'default',
};
-my $cpu_flag =
>>They are 2 missing hyper-v enlightments,
>>"hv-synic" & "hv-stimer"
>>
>>which helps to reduce vm exits
user on the forum has reported better result with theses 2 hyper-v enlightments,
keeping -no-hpet.
I don't known if it's planned to add qemu 2.12 soon, but we could had theses 2
enlightme
Le 24/06/2018 à 13:18, Detlef Bracker a écrit :
>
> *The questions:*
>
> A) What has destroyed the boot record of the VM of the Mail-Gateway?
> Hardware-Failures on the Host cant been (SSD-RAID - without wareout -
> SMART
> passed)
This is the only question which should be investigated.
> B) Why t
More Infos after many tests and my cognition is: the *proxmox backup is
absolute unsecure* and
can been the proxmox HA too - why a wrong MBR will then wrong on the
other machines too!
First find the problem - I thing it can been a bug in VMs on Proxmox 5.x
- yesterday after host reboot!
*The
10 matches
Mail list logo
