Latest activity
-
Ppulipulichen replied to the thread Using GCP Always Free e2-micro as a QDevice for a 2-node Proxmox VE cluster: any pitfalls?.Thank you so much for sharing your test results! It’s amazing to know that even latency of up to 1s is still workable for the QDevice. That is truly a valuable piece of real-world experience. I also completely appreciate your point regarding the...
-
Mmunchworker replied to the thread [SOLVED] Trying to enable nested virtualization results in perfomance loss on vm.I checked and there is no driver support for our nvidia card on either 6.17 nor 7.0 Kernel :( so that is currently not an option.
-
Sstevehughes posted the thread Nested ESXi VM hangs on boot in Proxmox VE: Installation and configuration.My PVE cluster is 6 hosts with AMD EPYC 24core CPUs and 1TB RAM each, running 9.1.4. I want to function as a DR site for a client who runs vSphere. To this end I want to build a few large nested ESXi 8.0 VMs. I've installed ESXi in a VM, and it...
-
GGMBauer replied to the thread [SOLVED] RAM in Proxmox nur teilweise erkannt - 188 GB von 256 GB.Hey Leute, das ist erstens kein Serverboard und zweitens ist die ganze Hardware... naja, sagen wir mal "refurbished". Ich bin mir sehr sicher, dass der TE das nicht produktiv verwendet. Ich hoffe es zumindest...
-
GGMBauer reacted to Scoobydru's post in the thread [SOLVED] Windows Server 2025 Standard startet nach heutigem Update nicht mehr with
Like.
Hi Neobin, I only joined to say "thank you" the downgrade worked a charm Regards -
WWeltherrscher replied to the thread Opt-in Linux 7.0 Kernel for Proxmox VE 9 available.Ok, I narrowed my problems down to either the 16.4 nvidia enterprise host driver and / or the kernel option "iommu=pt". After 6.17 showed the same failures I tracked my last actions on the server which were the installation of the nvidia driver...
-
DDultas replied to the thread Proxmox can't restore from backup and deleted the LXC I was trying to restore.Was able to resolve using pct restore. Seems the UI was doing a check on the debian version that was seemingly unnecessary.
-
Jjaynguyen replied to the thread [TUTORIAL] Automated Installation + PXE boot.I think you forgot this option or type wrong name image (e.g "initrd.img" instead of "initrd-custom.img")
-
-
Ppulipulichen reacted to UdoB's post in the thread Using GCP Always Free e2-micro as a QDevice for a 2-node Proxmox VE cluster: any pitfalls? with Like.
Yes. I had tested high latency some time ago: https://forum.proxmox.com/threads/qdevice-deployment.173182/post-805735 Probably none, but I do not use it, so I can not tell. But involving a device "on the other side of the internet" is the exact...
-
Iivenae replied to the thread [SOLVED] Windows Server 2025 Standard startet nach heutigem Update nicht mehr.Als großzügiger Nutzer von No Subscription muss ich leider sagen, dass ich halt einfach mit so etwas leben muss. Ich mache die Updates monatlich (automatisiert) und starte nur ca. 1/4 der Kisten in der gleichen Nacht neu, die anderen warten 24...
-
NNevuly replied to the thread [TUTORIAL] Configuring Fusion-Io (SanDisk) ioDrive, ioDrive2, ioScale and ioScale2 cards with Proxmox.A critical error occurs in the latest update (7.0 kernel) when using SATA Passthrough or PCIe Passthrough for the ioDrive2. This issue has currently been reported, so please wait until it is resolved.
-
Bbossanova808 replied to the thread Asymmetric Tailscale speed issue with Kernel 7 and multiple NIC types.VM - same results (as others have also reported). Host - I do not want Tailscale on the host (but iperf3 performance without Tailscale is fine).
-
Bbhoriss_viahn replied to the thread Error: Device /dev/dri/card0 does not exist after LXC update.I had the same problem today while installing Immich from the community scripts It broke my GPU passthrough to existing LXCs like Jellyfin (and also broke it's own installation). It also made an existing SMB/cifs share unavailable until I...
-
Ssgp replied to the thread proxmox-backup-client notification on failed/successful backup.For some time I had the PB-client failing backup (the cause being out of memory). Meanwhile, PBS had shown the following: %time%: backup ended and finish failed: backup ended but finished state is not set. %time%: removing unfinished backup...
-
JHi all, I have an Ubuntu LXC container running on Proxmox. There is no firewall enabled on the container, and I can SSH into the LXC without any issue. The problem is that when I try to SSH from the LXC to a server outside of Proxmox, the...
-
DDultas posted the thread Proxmox can't restore from backup and deleted the LXC I was trying to restore in Proxmox VE: Installation and configuration.I had an LXC that I needed to restore from backup. I understand that the existing data needs to be erased to be restored from backup but I did not expect it to fail and completely nuke the LXC in the process. While restoring I got the error "TASK...
-
TTacioandrade replied to the thread [SOLVED] Support for PERC H310 Mini on PVE9.Friends, sorry for the delay in replying! I ended up having several problems. After a thorough analysis, it turns out that this board no longer supports Proxmox, even with the newest kernels. The options I found were: * Change the firmware to...
-
Ffw1976 replied to the thread [SOLVED] Windows Server 2025 Standard startet nach heutigem Update nicht mehr.Nach den jetzigen Updates funktioniert nun alles wieder wie gewohnt. Herzlichen Dank an die Entwicklung!
-
JJohannes S reacted to celemine1gig's post in the thread [SOLVED] RAM in Proxmox nur teilweise erkannt - 188 GB von 256 GB with Like.
"Interessante" Denkweise. :) Ich hoffe du nimmst mir den folgenden Kommentar nicht übel, aber Ahnung von Hardware scheinst du nicht viel zu haben, oder? Gerade weil das die Maximalausstattung deines Boards ist, ist das immer potenziell...
-
Aanutrix replied to the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now.To list the installed kernels: proxmox-boot-tool kernel list In my case, I had `6.17.13-8-pve`. To pin it for next 1 boot to test out a kernel: proxmox-boot-tool kernel pin 6.17.13-8-pve --next-boot Then, reboot. To pin it so it stays the same...
