Search results

I followed the steps to install the 6.5 kernel and it seems to be working without any problems. The only anomalous situation is that I now receive an email every time a backup is performed. In the backup configuration I have the option to just warn when it fails. EDIT: I have reconfigured the...

I was having this same problem and have posted a few months ago https://forum.proxmox.com/threads/vms-freeze-with-100-cpu.127459/post-560869 what i had done that somehow mitigated the problem. One of them was disabling KSM. Since then the problem have not repeated. I would like to try with the...

Understood...Thanks.

Great work proxmox team. I have a small doubt. In the prerequisites you say "Co-installed Proxmox Backup Server should wait until a public beta or final version will be released". Does that mean that if a have a PBS as a VM on my proxmox host i must not update yet and wait for a PBS beta at least?

I have this error when executing "apt update": W: Skipping acquire of configured file 'pve-no-subscription/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pve bookworm InRelease' doesn't have the component 'pve-no-subscription' (component misspelt in sources.list?) W...

I have a similar problem with a Windows Server 2022 Vm on an HP PROLIANT 360G9 server. Everything is up to date and i use the latest 6.2 kernel. Sometimes this vm started using 100% cpu and froze. Then my rdp users, around 50 of them, get disconnected. I have taken some steps that somehow have...

Had the same problem. Just updated with latest updates few minutes ago and it works again.

I also instaled the 5.15 kernel and everything looks ok. Will try it in the coming days.

After booting 5.11 kernel the problem disappeared. In the images you can see de diference.

Booting with 5.11 kernel seems to solve the problem. Will report back after some more testing.

On a windows server 2019 vm the cpu load was on average 15% and now it is more than 60%. This machine was already on proxmox 7.1 and working fine. Yesterday i updated it with latest kernel and qemu. The scaling governor is set to perfromance also.

I have the same problem since yesterday after updating to latest kernel and Qemu version. The memory integrity was already disabled and the problem is the same.

Just renamed etc/udev/rules.d/70-persistent-net.rules, rebooted and the new predictable interface names came up. After adjusting my brigdes on proxmox interface everything is working fine. Will do more reboots for testing purposes.

Thanks for your help. If I install proxmox 7 from scratch on a new disk will it be fixed since interface naming will be updated?

Hi. Since i updated to Proxmox 7 i have a strange problem with my Pfsense VM. I have 2 intel nics (eth0 and eth2) used only by pfsense VM, one for lan and the other to wan. Sometimes when a reboot the server, pfsense interfaces get switched so my wan become my lan interface and the lan become...

Instead of cifs i had configured nfs as my remote backup share and it works fine now.

Well, spoke too soon. Host down again. Will wait for new kernel and see if it resolve the problem.

Seems to have discovered the problem. Root was with low space and after freeing some space, it seems to work fine. Not the kernel after all. Will post later to confirm if still working.

Hi everyone. I have 2 servers with proxmox connected to a Freenas smb share for backups. One of them has been updated to the latest kernel and since then i have a problem with my cifs mount. If i try to use it, it says something like "host down". I have to force dismount and mount again and it...

I have reinstaled the kernel and it worked. Many thanks .