Ich habe die .302er mal in geklonten VMs getestet, Server 2022 und 2025. Auf zwei Systemen laufen u.a. SQL-DBs. Bisher habe ich in diversen Last-Szenarios (Sql burn-in bei parallelem Schreibzugriff und gleichzeitig vielen requests via Netzwerk)...
Ich habe die .302er mal in geklonten VMs getestet, Server 2022 und 2025. Auf zwei Systemen laufen u.a. SQL-DBs. Bisher habe ich in diversen Last-Szenarios (Sql burn-in bei parallelem Schreibzugriff und gleichzeitig vielen requests via Netzwerk)...
Alright, the fact that it worked with the firewall being disabled narrows down the issue.
It seems like the NFS mount daemon (rpc.mountd) might be using a random port, which then in turn is blocked by the ufw.
Configuring a fixed port here and...
Is it though? According to @gurubert in https://forum.proxmox.com/threads/problem-with-pve-8-1-and-ocfs2-shared-storage-with-io_uring.140273/ it doesn't seem to be maintained. That thread is older though so things might have changed since them...
Some times its the router port it selves the Problem.
Please check: put a simple non management 5 or 8 Port 1 GBit/s Switch between your router and your proxmox ve host.
Please write your Dell representative and ask them for proper PVE support. The more people ask this, maybe they'll work something out. Unless this happens and maybe hell frozes over, I fully agree with @bbgeek17.
Hi @Jianming , you can now use PVE with iSCSI storage with LVM overlay and snapshots.
However, thin provisioning will need to come from the array at this point in time.
These articles may be helpful to you...
Why? The main reason people run into issues isn't the layout of the UI but that they don't have a dedicated cluster network for corosync. And this they will need anyhow because otherwise you wouldn't be able to communicate the cluster...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
ok, so while I could not figure out how/when that broke (if it was ever functional..) i sent a fix now:
https://lore.proxmox.com/pve-devel/20260902074338.914500-1-d.csapak@proxmox.com/T/#t
thanks for reporting...
Here is a Video for Proxmox an Raspeberry Pi using RaspberryOS lite. It is in french but can be watched with autmatet translation to english.
https://www.youtube.com/watch?v=XXkkUZNR6xQ&t=405s
I ran into the same warning after upgrading from PVE 8 to PVE 9 with Ceph Squid.
It looks like /etc/init.d/ceph is simply an obsolete conffile left behind by ceph-base:
# dpkg -S /etc/init.d/ceph
ceph-base: /etc/init.d/ceph
# dpkg-query -W...
Please call on the proxmox ve root console:
ip addr show
ip route show
ethtool <device name> # <device name> is something like eth[0-9]+, enp[0-9]+s or eno[0-9]+, see 1st results
#on new installations mybe other names