Recent content by albgen

Dears, i have a very strange issue and basically on the logs i see the following: root@SrvAuct2807206 ~ # journalctl --since "2025-10-10 00:00" --until "2025-10-11 23:59" | grep -i "watchdog" Oct 10 13:24:33 SrvAuct2807206 watchdog-mux[898]: got terminate request Oct 10 13:24:33 SrvAuct2807206...

they replace the specific hardware so ssd, motherboard etc but not a copy of the whole existing machine :(

root@AX1011728574 ~ # cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 nvme1n1p1[1] nvme0n1p1[0] 262080 blocks super 1.0 [2/2] [UU] md2 : active raid1 nvme1n1p3[1] nvme0n1p3[0] 1046528 blocks super 1.2...

the reboot 06:30:12 was made by me.

yes, 2 NVMe SSD Disks which are in Raid 1. mdstat is not installed. -bash: mdstat: command not found

hi David, but server doesn't have any SATA devices connected.

Hi, i'm running Proxmox VE 7.1-12 and today i faced a strange issue. I have checked the journal file but no anomaly found(attached). At 06.00AM in the morning :), a customer calles and tells me that nothing is working. Started the troubleshooting and found that it was an issue with the virtual...

It's a module in the kernel or something else?

Hello, i have a 3CX(latest version which is a debian based) on prem installation running on Proxmox 8.1.8. This VM has 12GB of RAM and the hotplug(on Options) was enabled for Memory and CPU and thus NUMA was needed to be enabled at CPU config so that the machine could run. Everything was...

i thought the snapshot mode was also backing up the RAM. It would be better to remove at all this mode or there are use cases when it's useful?

Dears hello, I just wanted to move some VMs from one Proxmox installation to another. Usually when i have to do this kind of operation, i stop the vm, start a scp copy of the disk and the config file and all works perfectly. This time wanted to change and use the backup functionality...

yes tom, true, but but you know, reading hundreds of pages is not very simple. Currently i use proxmox for development environments and the reason is exactly this. The learning curves and the suprises :) It would be nice to show a warning to the user when he is dealing with the disk of a vm. In...

AndrzejL you are right. This is a big limitation and it is not even warned the user when importing or creating a vm with vmdk.

ok, but dont kill a random machine...just be more intelligent..kill the one that at least is in starting status...

hi, proxmox was right, i mean the RAM was less than the total needed to run the VMs. The issue though is that, proxmox should not attempt to start a VM when there is no ram available. The current behavior, which means it will kill a random vm when there is no ram, is very dangerous. I mean i...