Recent content by Moayad

Could you please post the kernel command line `cat /proc/cmdline`? EDIT: As well as the output of `pveversion -v`. I would also check the BIOS/Firmware and microcode [0] if up-to-date, [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_firmware_cpu

Yes if you'd like to silence it, you can add the options to your existing kernel command like root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off video=efifb:off video=vesafb:off Then: proxmox-boot-tool refresh reboot

Thank you! Could you please post the output of `dmesg |grep EDID` command? And if if you have VMs could you provide the VM config `qm config <VMID>`? I guess this message is related to monitor or GPU not to Proxmox VE, and it's not harmless. But I would to make sure from the output of `dmesg`.

Thank you for the output! Just to confirm what exactly template version you used for Alma10? Could you please set nameserver using `--nameserver` flag using `pct set --nameserver 8.8.8.8 100` (change the nameserver to your nameserver IP) or add that in the CT config?

Hi, May you please provide us more details? - The PVE installed successfully? - What storage you are using for the root LVM, ZFS, or BTRFS? - Have you checked the dmesg?

Hi, I would compare the following, if the AlmaLinux 10 CT have the same config where the other CT works: cat /etc/resolv.conf ping -c3 google.com ping -c3 8.8.8.8 As well as the CT config `pct config <CTID>` this will help if the issue is realted to the AlmaLinux Image or to DNS configuration...

Hi, Have you tried `pvecm updatecerts --force`? Do you have a cluster or only one single node?

Hi, If you have the same/similar issue, could you please check the hostname? Otherwise, could you open a new thread or provide us with more information about the issue?

Hi, Could you please provide more details i.e., the output of the below commands: lvs -a pvesm status And the LX config `pct config 101`

Thank you! Could please check the syslog and the corosync status `systemctl status corosync` on the `xypvele50` node, plus test ping to .43 and .48. You can check the syslog using journalctl tool as the following command: journalctl --since "2 days ago"

Hi, First of all I would check the bash/zsh history to see why the interfaces file was empty! Regarding the issue, could you please post the output of the following commands: pvecm status cat /etc/pve/corosync.conf pveceph status

Hi, Have you tried older PVE kernel? Did you checked the `dmesg`?

Hi, What is the output of `pveversion -v`?

Hi, Thank you for the log you've provided! For more information before I reply the actual reason of the issue cause, could you please provide us the `/etc/pve/corosync.conf` and the network configuration `/etc/network/interfaces` as well as the `ip a` output? This should help us to take an...

Hi, Did you check our wiki guide [0]? If yes, could you please specify what you want help with? This will help us provide you more assistance. [0] https://pve.proxmox.com/wiki/Multipath