Search results

  1. M

    [SOLVED] Should I use KernelCare?

    Has anything changed since then? Can we safely use KernelCare with the latest PVE?
  2. M

    kernelupdate without reboot

    I'm interested in this, too.
  3. M

    Possible bug when renaming a security group

    Hello When I rename a firewall security group (on the cluster/dc level), it won't get renamed on the VM level and thus the security group no longer applies to that VM. Is that a bug or intended behaviour? Thanks.
  4. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Thank you Fabian! Alternatively, enabling 'krbd' also fixes the issue for now. :)
  5. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Many thanks for the suggestion!
  6. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    cpool is a ceph pool in my cluster.
  7. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Yes, it happens reliably 100% of the time. The PBS load is ~0% (nothing happening), same with the node. The issue happens regardless of whether the VM is on or off. agent: 1 balloon: 131072 bios: ovmf boot: order=scsi0;net0 cores: 35 efidisk0: cpool:vm-110-disk-2,efitype=4m,size=528K memory...
  8. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Yes, but I don't quite understand what to do now. Do we need to downgrade pve-qemu-kvm on all our nodes? If yes, will it affect stability of the cluster? @Fabian_E would be great to hear some recommendations.
  9. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    @GrueneNeun Try apt install pve-qemu-kvm=6.1.1-2, restart the VM, and then back up again.
  10. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Moving to pve-qemu-kvm=6.2.0-1 reproduces the unable to connect to VM error
  11. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Upon doing the first couple of tests, it seems like there are no 'unable to connect to VM' errors anymore after the downgrade, when both backing up to CephFS and Proxmox Backup Server.
  12. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Same.
  13. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Confirmed. Works in 7.1-1.
  14. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    7.1 I believe its a bug anyway, so 'assistance' won't help that much.
  15. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Will anyone from Proxmox visit this thread? This is a critical issue as we can't make any backups now.
  16. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    Same. It happens even with empty just-created disks.
  17. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    True. It seems like it only affects VMs with large disks attached. I was forced to disable all backups, its a major and critical issue that should be sorted out! In my cluster, it only happens when a harddisk is large enough (e.g. 1TB or more). Backing up locally, I get: VM 18723 qmp command...
  18. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    No, its a remote destination. I also tried backing up to a local storage, same. journatctl shows: May 10 10:29:29 p01 pvedaemon[1463275]: VM 18723 qmp command failed - VM 18723 qmp command 'query-pbs-bitmap-info' failed - got timeout May 10 10:29:32 p01 pvedaemon[3914617]: VM 18723 qmp command...
  19. M

    Backup to PBS failed - qmp command 'query-pbs-bitmap-info' failed - got timeout

    The same problem on 7.2-3.
  20. M

    Possible bug after upgrading to 7.2: VM freeze if backing up large disks

    PVE latest, just updated to 7.2. Guest OS is AlmaLinux, but I think it doesn't matter as the same 'hang' happens even if the VM is off.
Top Bottom
Back