Latest activity
-
EThis is expected behavior with Proxmox HA. If a VM is managed by HA, stopping it is generally interpreted as an unexpected state, so the HA manager will try to bring it back online. For planned maintenance, you can temporarily put the VM into a...
-
EYou can also change the VM HA state from "started" to "igniored". VM -> Upper right corner: [More] -> manage HA Then do your changes/testing/restart(s) , and when you are finished change back to "started".
-
E@esnmb Proxmox HA is more of a “what state is it supposed to be” thing. PVE doesn’t know why it is off, it just knows it’s supposed to be running. The web GUI tells HA it should be stopped therefore the guest is asked to stop.
-
EMost likely something network related or storage related. If it's shared storage, then you're just migrating RAM while a VM is running. If it's an LXC or the VM is off, hardly anything is actually moved so something to do with the locking on the...
-
JJvB replied to the thread VM becomes unresponsive during Veeam backup.We use many more Veeam products and features. VSPC, Cloud Connect etc. Proxmox Backup Server is not able to give us all features we need in our multi-tenant private cloud.
-
Llonger replied to the thread Proxmox random reboots.You can use root@pve~# last reboot --fulltimes --limit 50
-
Ssantiagobiali replied to the thread Win2025 retrim fails with "Data error (cyclic redundancy check). (0x80070017)" while Win11 OK.Note: virtio-win-0.1.302-1 released today did not fix this issue. event: The storage optimizer couldn't complete retrim on (C:\ because: Incorrect function. (0x80070001)
-
MMarkusKo replied to the thread Grub hangs when loading initramfs.have you tried "nomodeset" in grub? https://pve.proxmox.com/wiki/Installation#nomodeset_kernel_param
-
Mmaxim.webster replied to the thread **Bug: remote node shell forces `LC_ALL=C`, breaking UTF-8 character width handling**.-> https://bugzilla.proxmox.com/
-
Iidoc posted the thread **Bug: remote node shell forces `LC_ALL=C`, breaking UTF-8 character width handling** in Proxmox VE: Installation and configuration.On a PVE cluster I noticed that xterm.js shells behave differently depending on whether the shell is opened on the node serving the Web UI or on another cluster node. Reproduction: * Open the PVE Web UI on node A. * Open `Shell` for node A...
-
LLaimonas Vijūnas replied to the thread Proxmox random reboots.At the moment I am running on 7.0.14-14-pve. I didn't document previous version but I install updates every 4 weeks, so it can't be large jump. Installed updates on Sunday, server started to acting strange on Tuesday. Today I installed latest...
-
-
JYes, it's probably not necessary in practice but it remains ironic: that which makes check-summing redundant filesystems perfect for swap is exactly what makes them impossible to use for swap. I guess a md-raid1 of multiple md-integrity (without...
-
Aa0ii22 replied to the thread Grub hangs when loading initramfs.Try removing the nvidia card and booting into the installer. If that works then you know it is the nvidia drivers. You can blacklist the module to get your normal boot and work from there.
-
LLaimonas Vijūnas replied to the thread Proxmox random reboots.It's not cluster. journalctl -b | grep "system reset reason" gives no output It's ASUS motherboard ( if I remember correctly), so sadly no Ipmi/Idrac. On last reboot found never seen log entry: Aug 28 13:17:44 test QEMU[2319]: ehci: PERIODIC...
-
Jjoe-pow replied to the thread [SOLVED] System Log - Live Mode stopped working.Thanks @clangren. Had the same issue on a 2-node cluster. The problem was on one node upgraded from a bookworm-installation which had still rsyslog running. Purged rsyslog and then the "vacuum-time" trick did the job.
-
Llonger replied to the thread Proxmox random reboots.-Did you rule out fencing in case it is a cluster node? - Does Previous system reset reason shows something interesting? journalctl -b | grep "system reset reason" Do you have in IPMI/iDRAC? does it show anything in health event logs/sensor reading?
-
MThe /usr/sbin/shutdown command (run from the console or cron) will shutdown Proxmox in the same way as shutting down Proxmox from the web GUI. It also allows you to specify a specific time as well. This is a well known Linux command and there are...
-
MAnd you don't need to shutdown guests before that. Just add a 0 1 * * * root /usr/sbin/shutdown -h now to /etc/crontab and it should shutdown the server each day at 1 at night. But keep in mind that this won't check if important tasks are still...
-
LLaimonas Vijūnas posted the thread Proxmox random reboots in Proxmox VE: Installation and configuration.It all started when I updated to 9.2.11 using pve-no-subscription repositories. Proxmox reboots randomly after 10-20 minutes. Can't find anything meaningful in logs, except : Aug 28 13:12:46 test pvestatd[1820]: storage 'Buffalo' is not online...
-
Falk R. replied to the thread VM Disks nach dem Verschieben auf anderes Storage defekt/korrupt.Ich sehe bei anderen Storages nach dem löschen eines LV (VM Disk) dass ein Reclaim auf dem Pool startet. Da wird Speicher frei gegeben und somit im Background ausgenullt. Eventuell liegt das daran, dass ich eine VM Disk gelöscht habe wo Discard...
