Naja, Proxmox kann ja nicht unbedingt etwas für Hardware-Defekte. Und die PVE-Installation ist vermutlich schneller wieder eingerichtet, als die ioBroker-Installation, oder?
Sehr gut, dass Du die Backups vom Server holen konntest. Falls Du ein...
This „smells“ more like a PCIe/BIOS power management problem than a Proxmox config error. A quick test would be to swap the RTX cards in this slot and check, if the error persists with the swapped card.
What you could check before and after the...
ProxmoxVE doesn't use ifupdown but ifupdown2. That's the reason you have do do it via an reinstall of ifupdown2 instead of ifupdown. I wonder however how such an error is even possible shouldn't the normal update Procedure take care you don't end...
Was wenn du im "Monitor" der VM "info balloon" eintippst? Vergleich den Output mit einer VM wo die Gast Sicht der RAM Anzeige wie erwartet klappt.
Denn der Guest Agent wird nicht für die Abfrage der RAM Auslastung aus Gast Sicht benötigt. Hier...
Greetings! The Proxmox installation and configuration manual I published earlier this year (https://forum.proxmox.com/threads/proxmox-installation-and-configuration-manual.181116/#post-840113) has been updated with inclusions for critical...
The content seems fine. I just picked a very few pages and read them quickly/fast - I dug into them only slightly. (And English is not my native language...)
Unfortunately still having the same issue even with 7.x kernel:
Linux pve 7.0.2-6-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.2-6 (2026-05-20T08:55Z) x86_64 GNU/Linux
2026-05-25T04:56:28.342706+00:00 pve kernel: Call Trace...
If you lost connectivity after purging ifupdown (which removes stuff that also belongs to ifupdown2), manually creating /run/network/ and (re)starting networking services should get you going again.
Once you have a working network connection...
Ah. I ran the PS thing on a VM that did NOT have UEFI. So ya. It choked.
It works fine everywhere else I tried it.
PS C:\Users\tcabernoch> [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2
023'...
Ran into similar issue, turned out the issue for me is that vfio_pci messed up with power state, below module param worked for me.
# or just adding vfio-pci.disable_idle_d3=1 to the kernel cmdline
sudo insmod vfio_pci.ko disable_idle_d3=1
I hit the same problem. For me the solution was to use create a new instance of the zfs-import@.service with a symbolic link by running this command (pool was named mainpool, adjust accordingly):
ln -s /lib/systemd/system/zfs-import@.service...
What command? Both of them are standard, registry edits and scheduled taks runs. You can find them elsewhere in case there is a typo.
You do need an updated/supported Windows 10/Server 2019 or higher.
The Linux systems don’t have a problem...
Hi guys, just need your help,
Setup:
Proxmox VE 8 (kernel 6.x PVE)
4× NVIDIA RTX 6000 Ada (AD102) for VM passthrough
All 8 functions (4× GPU + 4× HDMI audio) bound to vfio-pci
IOMMU on, intel_iommu=on iommu=pt, ACS working, groups clean
q35...