Search results

  1. D

    Live VM Migration fails

    If I set the MTU to 1500 on the network interface over vmbr2, the migration still fails, and the logs show that it attempts to set the MTU to 9000 The bug report you're referencing is from 2017 and has also been closed. Are you going to investigate anything else, or is the solution...
  2. D

    Live VM Migration fails

    I've found the following: A machine with its network on vmbr2 fails to migrate, but if I use a bridge created with SDN (without touching the MTU), the migration from Proxmox 8 to Proxmox 9 completes without issues. A machine with its network on vmbr2 migrates correctly between nodes with...
  3. D

    Live VM Migration fails

    Hi, Full log Sep 02 11:31:48 proxovhgra-2401 kernel: tap1001002i0: entered promiscuous mode Sep 02 11:31:48 proxovhgra-2401 ovs-vsctl[2182816]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port tap1001002i0 Sep 02 11:31:48 proxovhgra-2401 ovs-vsctl[2182816]...
  4. D

    Live VM Migration fails

    Hello, I'll explain my situation a bit better: We have a 9-node cluster, and until yesterday, VM migrations were working normally. I updated one node to Proxmox 9, and any VM I try to migrate to it fails with an error. Yesterday, I tried changing the machine type to q35, and it worked, but...
  5. D

    Live VM Migration fails

    Hi, i have the same error Migration of a VM with Q35 works fine, but a VM with Default (i440fx) ends with errors. () 2025-09-01 15:25:31 starting migration of VM 146245 to node 'xxxx' (xxxx) 2025-09-01 15:25:31 starting VM 146245 on remote node 'xxxxx' 2025-09-01 15:25:33 start remote tunnel...
  6. D

    Kernel panic on migrated machines

    Here is the command output grep "PK[ER]" OSPKE CR4.PKE and RDPKRU/WRPKRU = true PKRU state = true PKRU features (0xd/9): PKRU save state byte size = 0x00000008 (8) PKRU save state byte offset = 0x00000980 (2432) OSPKE CR4.PKE and...
  7. D

    Kernel panic on migrated machines

    Hi, Finally, it only happened with two nodes in the cluster, any machine that was migrated froze, so we made the decision to turn off, move, and turn on. Now with the entire cluster in version 8 there is no problem. BR
  8. D

    Kernel panic on migrated machines

    Hello, we have a cluster with several servers running version 7.4, and we have already updated a couple of them to version 8. When we move machines from a server with version 7.4 to one with version 8.0, the machines experience kernel panic. This happens with different operating systems and...
  9. D

    Proxmox VE 8.0 released!

    Hello, we have a cluster with several servers running version 7.4, and we have already updated a couple of them to version 8. When we move machines from a server with version 7.4 to one with version 8.0, the machines experience kernel panic. This happens with different operating systems and...
  10. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    Hi, Try with qemu-system-x86_64 -enable-kvm -smp 4 -m 4096 -bios /usr/share/ovmf/OVMF.fd -boot d -cdrom ./proxmox-ve_7.1-2.iso -drive file=/dev/sda,format=raw,media=disk -drive file=/dev/sdb,format=raw,media=disk -vnc 127.0.0.1:1 BR
  11. D

    qmp command 'guest-fsfreeze-thaw' failed - got timeout

    I think that all problems are caused by qemu agent, for example: INFO: Starting Backup of VM 801036 (qemu) INFO: Backup started at 2020-10-15 08:32:55 INFO: status = running INFO: VM Name: xxxxx INFO: include disk 'virtio0' 'zfs_ssd:vm-801036-disk-0' 50380M INFO: backup mode: snapshot INFO...
  12. D

    qmp command 'guest-fsfreeze-thaw' failed - got timeout

    Hi, ⚡ root@cloud  ~  df -h S.ficheros Tamaño Usados Disp Uso% Montado en /dev/vda1 31G 11G 19G 37% / udev 10M 0 10M 0% /dev tmpfs...
  13. D

    qmp command 'guest-fsfreeze-thaw' failed - got timeout

    Hi, More details: All backups of the task with errors INFO: Starting Backup of VM 3019 (qemu) INFO: Backup started at 2020-10-14 08:30:02 INFO: status = running INFO: VM Name: xxx INFO: include disk 'virtio0' 'zfs_nvme:vm-3019-disk-0' 32G INFO: include disk 'virtio1' 'zfs_nvme:vm-3019-disk-1'...
  14. D

    qmp command 'guest-fsfreeze-thaw' failed - got timeout

    Hi, more details: vm backup that has been running for a week without problem INFO: Starting Backup of VM 801049 (qemu) INFO: Backup started at 2020-10-13 13:52:26 INFO: status = running INFO: VM Name: xxxxxxxxxxx INFO: include disk 'virtio0' 'zfs_nvme:vm-801049-disk-0' 22732M INFO: backup...
  15. D

    not sure if it is related but had something bad happen today

    Hi, We have the same problem in a cluster proxmox of ten servers and it's related to this https://forum.proxmox.com/threads/qmp-command-guest-fsfreeze-thaw-failed-got-timeout.77195/ When this happens "ERROR: VM 251101 qmp command 'guest-fsfreeze-thaw' failed - got timeout" in several tasks at...
  16. D

    qmp command 'guest-fsfreeze-thaw' failed - got timeout

    Hi, Yesterday we had many failed tasks with this error: INFO: issuing guest-agent 'fs-freeze' command INFO: issuing guest-agent 'fs-thaw' command ERROR: VM 251101 qmp command 'guest-fsfreeze-thaw' failed - got timeout ERROR: VM 251101 qmp command 'backup' failed - got timeout ERROR: Backup of...
  17. D

    Cannot allocate more than 1GB of ram after ram hotplug enabled [UBUNTU 20.04]

    Hi, cmdline of my vm is: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1024-kvm root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro memhp_default_state=online console=tty1 console=ttyS0 panic=-1 But not works
  18. D

    Cannot allocate more than 1GB of ram after ram hotplug enabled [UBUNTU 20.04]

    I'm trying to assign 4GB of ram to a virtual machine, but after I enabled hotplug for memory and cpu, the ram that the vm sees is not 991 (actually 1GB). Before enabling the hotplug, it worked as as expected. The problem only appears with ubuntu 20.04 and the cmline is: ~$ cat /proc/cmdline...
  19. D

    Error when finishing task of backup

    Hi, I've downgraded to 0.8-16 and there are no errors. BR
  20. D

    Error when finishing task of backup

    Hi, Yesterday, before upgrading to 0.8-17 the task of backup was completed without errors and without freeze the vm INFO: 97% (5.6 GiB of 5.8 GiB) in 3m 45s, read: 77.3 MiB/s, write: 77.3 MiB/s INFO: 100% (5.8 GiB of 5.8 GiB) in 3m 47s, read: 60.0 MiB/s, write: 60.0 MiB/s INFO: backup was...