Search results

PVE require root via ssh for cluster function.

Disabled power saving states on the Dell? Firmware updated? SSDs are enterprise or desktop versions? I have feeling, you have disk problem, missing virtio drivers in Window VMs etc, but nothing concrete, no VM config/pve versions written. Maybe install netdata and check the problematic time window.

MTU is 1500 for all servers, switches has 9216. Remotes the same location, the same switch and vlan. Because internal CA, fingeprints (FP): Configured for REMOTE1:8006: from pveproxy-ssl.pem FP - BUT - it automatically detects intermediate certificate FP and not client certificate FP Not...

Nothing spotted yet, because remotes are in production and there is nothing non-standard even on netdata (i can miss something of course). Today 4x test moving real vm 10+200 GB, migration fails for 2nd disk around 17-19/16-17 GB position. Moving via ssh/dd succeeded on the 1st try. Only...

Fix your time synchronization as the first step. clock skew detected on mon.proxmox03, mon.proxmox01

Tests 10 GB new VM (not recreated between this test round, the same VMID): 1. slowed down 598585344 bytes (8.6 GB, 8.0 GiB) copied, 39 s, 220 MB/s 8803647488 bytes (8.8 GB, 8.2 GiB) copied, 40 s, 220 MB/s 8878555136 bytes (8.9 GB, 8.3 GiB) copied, 41 s, 214 MB/s 8944156672 bytes (8.9 GB, 8.3...

https://pve.proxmox.com/wiki/Multipath

Created test VM1 with 10 GB and VM2 with 10+10 GB without any OS. Tested PDM migration: 1st try: VM1 slowed to hell 2nd try: VM2 succeeded Remotes tests: SERVER1: if=/dev/pve/vm-104-disk-1 bs=64k status=progress of=/dev/null - skipped due network test below SERVER2: of=/dev/datavg1/testimage...

Both sides are LVM thick (HP G8 servers with Pxxx smartaray raid10) src: 4 0 1573 1 20 0 179628 137020 hrtime Ss ? 272:12 pvestatd 0 0 1593 1 20 0 219244 175984 hrtime Ss ? 0:31 pvedaemon 1 0 15971 1593 20 0 265144 196768 do_epo S...

The same test as with Alpha version. The same remotes, upgraded to PVE 9. Migration of the 2nd disk stucked, manually stopped. Remotes: pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) 2025-09-19 11:28:53 remote: started tunnel worker...

That's not possible, because message doesn't exists on PMG after delivering to mailserver. So nothing to scan/learn again.

Don't use 8.2.2. You will have problem install another host with this version. Use last PVE version, now 8.4, or go directly to 9.

Filebackup of the host. Especially /etc/pve for pve specific configuration, large part of it is handled by cluster, but something is node dependent (example: certificates). Search forum at least.

Running PVE 9 on DL360/380 Gen 8-10 without problem. You can install rsyslog, attach monitor for kernel dump, maybe there will be something not in journal. It's standard debian anyway. Other thing - firmware, power, etc etc etc.

Without upgrading the 2nd SAN node: What will happen, when you shutdown the 2nd SAN node? What will happen, when you shutdown the 1st SAN node? I think, it's SAN support thing mainly, because with 2nd SAN node upgrading it blocks something, that can't be seen/logged from PVE side.

That's docker problem versus apparmor, not PVE related. Debian 12 didn't have active apparmor, but debian 13 has it by default. I encountered the same problem with giltab-runner + docker. Profile docker-default is created by docker service on the fly, so you have two options: 1]...

It's better to have container/vm for any service and leave proxmox doing only proxmox things.

Configure zimbra to move mails to spam folder. PMG is only gateway, not mailserver with mailboxes.

I have SAN with 3 luns connected with multiple destination's paths by multipath without problem. But i used mainly cli for configuration at the end, not gui. Looking on your debug, i think problem is somewhere 1] acl on SAN 2] iscsi/multipath misconfig Check...

Was it resolved? I got the same problem, finally upgraded one of the Dell 740XD from pve 7 to pve 8 (Linux pve-18 6.8.12-13-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-13 (2025-07-22T10:00Z) x86_64 GNU/Linux) and every reboot: Screen lost. Server stuck. Event Message: A fatal error was detected on a...