Search results

With all due respect, your opinion is based on your lack of experience in the Debian + Proxmox system

I think I'm a bit lost In our case: On Dell R240 or R340. Boot from JBoss RAID1 LVM 6.5.11-4-pve UEFI The server stops at initial ramdisk. It doesn't get up Same machines on 6.2.16-19-pve no problem /etc/default/grub: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2>...

In our case it's the same: https://forum.proxmox.com/threads/dell-r240-fail-to-start-after-kernel-update-6-5-11-3pve.136826/

Same problem on Dell R240. Boot from JBoss RAID1 LVM 6.5.11-4-pve Same machine on 6.2.16-19-pve no problem We find this: echo "simplefb" >> /etc/initramfs-tools/modules update-initramfs -u -k 6.5.11-4-pve (or update-initramfs -u -k all) # reboot But it doesn't solve the problem Same problem...

proxmox-ve: 7.2-1 (running kernel: 5.19.7-1-pve) live migration, storage Ceph: from Intel(R) Xeon(R) Silver 4310 CPU to Intel(R) Xeon(R) E-2234 CPU - OK from Intel(R) Xeon(R) E-2234 CPU to Intel(R) Xeon(R) Silver 4310 CPU - OK from Intel(R) Xeon(R) E-2234 CPU to Intel(R) Xeon(R) E-2234 CPU - OK

Is it a safe solution for production?

proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve) migration: from Intel(R) Xeon(R) Silver 4310 CPU to Intel(R) Xeon(R) E-2234 CPU - VMs froze using 100% CPU from Intel(R) Xeon(R) E-2234 CPU to Intel(R) Xeon(R) Silver 4310 CPU - OK from Intel(R) Xeon(R) E-2234 CPU to Intel(R) Xeon(R) E-2234 CPU - OK

pve-qemu-kvm 5.1.0-3 on PVE proxmox-backup-server 0.9.0-2 on PBS the problem does not exist

More information about the issue: PVE: proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve) or proxmox-ve: 6.2-2 (running kernel: 5.4.60-1-pve) PBS: problem on higher version than 0.8.16-1. PBS is VM with storage on RBD, free 900GB of the 4TB. PBS is remotely (other data center). Backup job at end...

Hello Same problem. Downgrade: on pbs console/terminal apt install proxmox-backup-server=0.8.16-1 reboot