Recent content by FrancisS

Hi Ali Thank you I bind the VM to the USB node with strict, set max_relocate=0 max_restart=1, the node do not restart, after a short time from the GUI the VM status unknown. The USB device 'Yubikey'. Best regards. Francis

Hello Elias Thank you ! I try this Similar to this: ha-manager rules add node-affinity usb-vm-rule --resources vm:<VMID> --nodes <node-name> --strict I restarted the node, go to maintenance, all the other VMs are migrated and nothing. For the restart to finish I have to manually stop the VM...

Hello, We have a VM with USB passthough that crash with the error "usb_packet_check_state". We need to restart automatically the VM. The cluster is configured with "shutdown_policy=migrate" (some VMs not in HA !) and the VM with HA state "ignored". If we set the VM with the "state=started"...

Hi, Thank you, I understand the change. Best regards. Francis

After the PVE upgrade 9.2.5 I cannot migrate VM. I have the message "Cannot migrate vm because ha resource vm:XXX is no-allowed on the selected target node" l have also some times the message "Cannot migrate conntrack state, target node is lacking support. Active network connections might get...

Hello torbho, You are right after a reboot the OSDs go "down"... and the system restart before the OSDs go "out". For the configuration "mon_osd_down_out_interval" we have the default 10mn. So no "noout" necessary, thank you. Francis

Hello Torbho, Thank you, I want to execute "ceph osd set noout" only when I reboot a node, not when a node "crash". The problem, some times the administrator do not execute the "ceph osd set noout" and after a node update "reboot" the node. After the updates he have to execute manually...

Hello, On a cluster with hyper-converged Ceph, is it possible to execute automatically the command "ceph osd set noout" when a node is rebooted ? (or shutdown (?) Best regards. Francis

Hello, For the next update of grub, "/boot/efi/EFI/debian/..." or "/boot/efi/EFI/proxmox/..." was updated ? Best regards. Francis

Hello, Same problem when I upgraded the PVE 8 to PVE 9. We installed PVE on top of Debian like PBS. Before upgrade After upgrade sum boot UEFI The system do not boot Manual correction boot UEFI (efibootmgr)

Hello, I follow this https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4 Best regards. Francis

Hello, Alter the upgrade to PBS 4 our PBS servers (PBS 3 install on top of Debian 12) do not boot and hang with the message The UEFI is configured to boot on "/boot/efi/EFI/debian/grubx64.efi" (debian install). The upgrade create a "/boot/efi/EFI/proxmox/grubx64.efi" and do not update...

Hello, Sorry for the late update, I replaced all the Crucial disks and now no slow messages... and no more performance "problems". Best regards. Francis

It is not part of the file

Daniel, l removed the "resources.cfg" and reconfigure HA (no rules change) Now no affinity problem the VMs with affinity "positive" are on the same node pve3. Thank you for your help/time Best regards. Francis