Search results

Das kann ich bestätigen. nmap --script path-mtu <vSwitch host> ... Host script results: |_path-mtu: PMTU == 1500

I have tried but didn't help, I will stick to turning it off this way: systemctl stop watchdog-mux.service ; sleep 1; ipmitool mc watchdog off

Thanks for this hint, I will give it a try at the next opportunity and report if it helped.

Hi All, I am using the latest PVE 5.4 and the builtin hardware watchdog in a Supermicro X11 board with the ipmi_watchdog kernel module. After rebooting the machine the baseboard management controller (AST2500) complains about a watchdog timeout and tries to reset the machine somewhere between...

worked for me, thanks!

The guest is Ubuntu 18.04 with latest updates/kernel. It happens since I deployed the VMs which is about 4 months ago so it had several kernels running and 3 guest agent versions. apt changelog qemu-guest-agent qemu (1:2.11+dfsg-1ubuntu7.6) bionic; urgency=medium [ Christian Ehrhardt ] *...

There seems to be an issue with the qemu guest agent, the replication is failing many times for some VMs if it is enabled and running. I tried to disable the freeze commands in /etc/qemu/qemu-ga.conf: [general] blacklist=guest-fsfreeze-freeze,guest-fsfreeze-thaw and see the difference in the...

After letting the replication run only on the HDD pool for a while I am very sure the SSD pool is causing the problem. I checked the parameters of both pools and compared them but no idea what the cause is. Could you please point me into the right direction what is special about ZFS on pure SSD?

I have 2 pools, first mirror of 2 SSDs, second mirror of 2 HDDs. I see when replication fails it is always the first VM disk which is on the SSD pool, could it be related to that? Both pools are configured with thin provision and disks have discard on, I have now moved all VM disks to the HDD...

Yes all nodes are identical in software and run the same kernel (from pve enterprise repository)

I am running a 3 node cluster with local storage (zfs) and latest version of pve: proxmox-ve: 5.2-2 (running kernel: 4.15.18-2-pve) pve-manager: 5.2-7 (running version: 5.2-7/8d88e66a) pve-kernel-4.15: 5.2-5 pve-kernel-4.15.18-2-pve: 4.15.18-20 pve-kernel-4.15.18-1-pve: 4.15.18-19 corosync...

If the fix is in the stable respectively enterprise repository, I couldn't find anything about this in the changelogs.

Since we would like to go into production with our cluster soon, it would be very helpful to know what is going on with this issue. Could any proxmox staff member please confirm?

Is this fix already in stable because I'm still having this issue?