No, our problem is not solved. we continue having the 5 minutes downtime when we move a VM from one proxmox server to another in same cluster. We also upgrade to 6.2 version, but the problem persist. Hetzner support staff tell us that the problem is in our proxmox machines/ VMs...
Coming back to the problem, it makes sense about mtu 1400. We have some connection failures and we have the feeling that not only the hetzner virtual switch must be configured with mtu 1400, but also all the virtual machines that belong to this virtual switch. Does anyone know how to configure...
I have some VMs (with VirtIO)
I have this setup and works like a charm, but... some VMs with virtio gets mtu:1400 but others VMs also with virtio did not (maintains the default mtu:1500). How can add individual mtu parameter to /etc/pve/qemu-server/xxx.conf ?
Yes, but when we made a live migration between proxmox servers, the VM need at least 5 minutes to get up online. Anyway, I don't know if hetzner has changed anything last weekend, since now I'm having problems in outbound.
Thanks for your questions. I can have any test if you need.
We have performed the tests that you comment, but they have not worked. When we stop receiving pings from the migrated VM, just after finishing the migration we launch the arping command that you suggest from the console of the migrated VM, but the ping is still inaccessible...
Same problem with our Hetzner Proxmox Cluster installation.
In our case, whe have 2 servers on Falkenstein
Network failure on live migration and offline migration of any VM from node-1 to node-2 and viceversa.
Can anyone contribute...
When I access to Administration -> Tracking Center i have the message "No data in database" and i have not any information. Also if I search any data for a receiver inside start and end dates, i have not any results
Could you have any clue about this ?