Recent content by RobFantini

I think the above may be related to having debian desktop installed on the pve system. lxc start / stop work okay now from gui and cli. now there is another issue. for vzdump backup of a kvm which is stopped , this error occurs, and the backup is not created . this show 1 ok and 2...

now from cli this one starts: pct start 34101 and this too: pct start 34201 I do not know why those start now and not before from cli.

and another lxc run_apparmor_parser: 906 Failed to run apparmor_parser on "/var/lib/lxc/34101/apparmor/lxc-34101_<-var-lib-lxc>": apparmor_parser: Unable to replace "lxc-34101_</var/lib/lxc>". Profile doesn't conform to protocol apparmor_prepare: 1078 Failed to load generated AppArmor profile...

reboot an lxc failed: :# pct start 34201 run_apparmor_parser: 906 Failed to run apparmor_parser on "/var/lib/lxc/34201/apparmor/lxc-34201_<-var-lib-lxc>": apparmor_parser: Unable to replace "lxc-34201_</var/lib/lxc>". Profile doesn't conform to protocol apparmor_prepare: 1078 Failed to load...

I had one more system which had an ifupdown2 issue after upgrade to Trixie. All 5 systems with ifupdown2 bug were solved with removing comments from /etc/network/interfaces . specifically the comment lines had a interface name within the comment line. These insterface files with those...

1- what are Q35 and i440fx? 2- post /etc/network/interfaces for vmbr on both nodes

I solved this . the node that would have migrations fail to and from needed an adjustment in /etc/network/interfaces . the other 4 nodes have vmbr3 set as: auto vmbr3 iface vmbr3 inet static address 10.1.10.7/24 gateway 10.1.10.1 bridge-ports bond3 bridge-stp...

what is ' sdn config' ? I see software defined network.

from a node that is okay to migrate live to: root@pve2:[~]:# pveversion -v proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve) pve-manager: 9.0.5 (running version: 9.0.5/9c5600b249dbfd2f) proxmox-kernel-helper: 9.0.3 proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2 proxmox-kernel-6.14: 6.14.8-2...

from a node that fails more info: root@pve5:[~]:# pveversion -v proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve) pve-manager: 9.0.5 (running version: 9.0.5/9c5600b249dbfd2f) proxmox-kernel-helper: 9.0.3 proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2 proxmox-kernel-6.14: 6.14.8-2...

here is a migration that worked to an old node: task started by HA resource agent 2025-08-21 15:40:39 conntrack state migration not supported or disabled, active connections might get dropped 2025-08-21 15:40:39 starting migration of VM 107 to node 'pve2' (10.10.0.2) 2025-08-21 15:40:39 starting...

I have 5 nodes. pve was recently installed on 2 of the nodes. I can live migrate to the 3 older nodes. The 2 newer nodes get this warning [ sometimes , sometimes no warning ] : conntrack state migration not supported or disabled, active connections might get dropped Live migration fails...

ceph mon remove pve4

I also noticed the ext4 part. However the issue starts 100% of the time when a node is in the process of shutting down for a reboot - shortly after the point it turns off osd , the hang starts at some or all of the remaining nodes. I did not think that ext4 had hnything to do with ceph...

Also: has anyone else had the same issue? It could be that I have done something uniquely wrong.