Best way to force it seems to start compilation on some VMs. Those VMs will then get segmentation faults (inside the VM). In host the above errors do occur (either immediately or with a small delay).
Hello there,
1.Check the power supply to the system. Fluctuations in power or insufficient power can cause hardware errors. If possible, try connecting the system to a different power source or using a power - conditioning device.
2. Virtualization Configuration
Review the VM configurations in Proxmox. Check the memory allocation, CPU assignment, and device passthrough settings for each VM. Make sure that they are set up correctly according to the requirements of the guest operating systems running inside the VMs.
Try creating a new, simple VM with minimal resources and see if it also exhibits the same problems. This can help you determine if the issue is specific to certain VM configurations or more general to the virtualization environment.
3. Software Updates
Update Proxmox to the latest version and any associated packages. Check the Proxmox update logs to see if there are any known issues or improvements related to the errors you're experiencing.
1) This is difficult to test. I only have the original PSU.
Not sure if this is an indicator againt being a PSU issue, but as said I had also crashes with low utilization (in proxmox).
Only during bootup CPU usage goes above 20%. Besides that 5-12%.
2) Everything is setup correctly. I had similar (or even worse) issues before moving from windows 11 host to proxmox host.
Win11 was first VirtualBox (only 2 VMs) and later VMWare (also 2 VMs).
3) Proxmox is up to date. No other logs except those listed above.
The specific error message indicates that "the kernel tried to execute an NX-protected page," which may be caused by malicious code or memory corruption.
Please try only one RAM inside for each RAM .
see if that works better?
ZTHawk replied at 2024-11-07 17:22
I have tested both RAM modules separately (said so in the first post; maybe not clear enough). Same ...
HI there
The error was corrected already.
Proxmox Hardware Monitoring Tools:
Proxmox supports monitoring hardware status through plugins. You can install and enable hardware monitoring tools such as lm-sensors, smbios, etc., to track CPU temperature, fan status, and other information in real-time, ensuring that resources in the virtualization environment are not overburdened.
Ensure that Proxmox System and Drivers Are Up to Date:
Make sure that both your Proxmox system and its drivers are running the latest versions. Sometimes, older versions of Proxmox or drivers may not fully support new hardware, which could affect the performance and hardware temperature control.
Crashed again with the very long error. Again alsmost no load.
No log in Proxmox. It was only visible on monitor (but no keyboard input was possible).
Running now a memtest86+.
Proxmox is up to date.
1) Is there any link to "Proxmox Hardware Monitoring Tools"?
2) What do you mean with "The error was corrected already"?
3) Just in case: Can you provide me the latest BIOS?
For BIOS
Please send us a picture of SN number and BIOS version .
So we would be able to know whether it is latest BIOS and send you files accordingly.
Here`s how to check your BIOS version: https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ
Post time 2024-10-30 04:57:30
Post time 2024-10-30 16:47:20
Author
