Search results

  1. A

    Realm ldaps broken

    In my case I eventually managed to solve this same issue adding `sslversion tlsv1_2` to `/etc/pve/domains.cfg` (Or just remove sslversion option). I previously had `sslversion tlsv1` that was working until proxmox 7.
  2. A

    ELevating LXC running Centos 7.9 to Alma 8

    I'm interested as well.
  3. A

    Kernel BUG CPU Soft lockup.(VM/HOST freezes)

    What about 5.19? https://forum.proxmox.com/threads/opt-in-linux-5-19-kernel-for-proxmox-ve-7-x-available.115090/
  4. A

    Node crash with CPU stuck

    You should try to install a previous version: 5.13.19-6-pve Look also this other post: https://forum.proxmox.com/threads/kernel-bug-cpu-soft-lockup.110059/
  5. A

    Node crash with CPU stuck

    Which kernel version are you using?
  6. A

    Proxmox Host Hard Freezing - Memtest Clean

    If you look at the logs related to the previous boot (before the reset) journalctl -b -1 Do you spot some useful message?
  7. A

    [SOLVED] Unable to pin kernel

    Yes. It works. Thank you.
  8. A

    x86/split lock detection

    I see these messages Jul 05 11:56:26 host3 kernel: x86/split lock detection: #AC: kvm/797055 took a split_lock trap at address: 0xfffff80016761edd as well, but I don't notice any storage or connectivity issue (VM's storage is located on local disks). Should I be concerned about these messages?
  9. A

    [SOLVED] Unable to pin kernel

    Since the upgrade to kernel 5.15.x, due to issue like these, https://forum.proxmox.com/threads/kernel-bug-cpu-soft-lockup.110059/ https://forum.proxmox.com/threads/proxmox-7-watchdog-hard-lockup-cpu.111725/ I would like to try to install and boot the 5.13 kernel. apt install pve-kernel-5.13...
  10. A

    3x6to in RAIDZ1 and proxmox 100% full with a 4.7To copy file

    Try to perform an fstrim insidie the VM with 10tb disk. But I suspect that this is due to zfs block size and/or how data replication works on raidz1, that is a bit complicated to explain for me (write amplification and so on).
  11. A

    [SOLVED] PVE 7 won't start CentOS 7 container

    Ok. I can confirm that it is related to CGroupv2. Oct 22 14:32:16 proxmox pve-lxc-hook-lxc-pre-start[291859]: CT 10001 does not support running in a pure cgroupv2 environment Already discussed here...
  12. A

    [SOLVED] PVE 7 won't start CentOS 7 container

    Same problem here. PVE 7 with latest packages from no-subscription repository. centos-7-default_20190926_amd64.tar.xz template root@proxmox:~# pct config 10001 arch: amd64 cores: 2 features: nesting=1 hostname: centosette memory: 2048 net0...
  13. A

    AMD EPYC based systems rebooting

    Do you have some VM in HA?
  14. A

    [SOLVED] Error restoring container Error: error extracting archive - error at entry "blk": failed to create device node: Operation not permitted (os error 1)

    Mmm. It happens to me restoring an unprivileged container to an unprivileged container using PBS.
  15. A

    CentOS8/Alma8/Rocky8: NetworkManager does not recognice ifcfg-eth0

    Well. If you don't want to edit /usr/share/perl5/PVE/LXC/Setup/CentOS.pm, you can prevent NetworkManager from handling the DNS configuration...
  16. A

    CentOS8/Alma8/Rocky8: NetworkManager does not recognice ifcfg-eth0

    Any news on that? There are not other workarounds (to apply inside the container) other than editing such script?
  17. A

    PVE Kernel doen't work after install

    Installing Proxmox 6.1-2 instead of 6.2-1, I'm able to boot the server. Then, I updated the system with apt-get dist-upgrade (enabling the no-subscription repository), and now I'm able to boot in pve 6.2-10
  18. A

    PVE Kernel doen't work after install

    @ggillesa69 same problem here. After the installation, the server continuously reboot. Did you managed to solve the issue?
  19. A

    VM IO freeze for 15 seconds when Ceph node reboot gracefully

    How many monitors, managers and osd do you have?
Top Bottom