Ok. I tried:
-boot to recovery mode
-remove "intel_iommu=on" from /etc/default/grub
-# update-grub
-reboot, normal boot
Same result. Boots to login screen, then immediately goes black.
-insert live boot usb
-boot to proxmox rescue boot
Same...
Hi everyone,
I’m running into a very strange networking/TLS issue on my Proxmox host and getting extremely infuriated - I’m looking for suggestions on what to test next.
The main symptom is that large HTTPS downloads fail with TLS/decryption...
rescue boot does the same thing---boots to login then goes black almost immediately
yes- the Intel iGPU is passed through to a VM using "intel_iommu=on"
I can run commands in recovery mode...
At this point, maybe it is easier to just reinstall Proxmox?
Is there a good way to create backups of Proxmox config files from the recovery mode CLI? I have backups for the VMs and LXCs, and the data on...
No.
For all of the troubleshooting we were doing earlier, I had the pve box connected to a monitor booted into recovery mode. That is where I observed the straight to black screen.
I just tried reconnecting the pve box to the network. The router...
Ok...so I tried deleting the unit file and rebooting Proxmox with a normal boot. The boot screen passed by without showing any obvious errors and went directly to the Proxmox shell, showing the correct IP address and asking for login.
This...
ok. just to clarify this out a bit----if I delete the unit file and boot up Proxmox without the 2TB problem drive mounted-----should I then be able to re-add the 2TB nvme drive to the database storage without damaging the subvolume mountpoints...
@Impact ---OK, progress!! I did zpool import flash then zfs list The subvolumes and associated mountpoints are listed. Furthermore, when I cd into the /flash/subvol-... directories, the expected data is present.
I think this confirms that the...
Ich bin nicht der OP, aber ich antworte dennoch mal..., nur zu Unterhaltungszwecken...
Naja..., warum nicht so arbeiten?
Ich verwende PVE extensiv an mehreren Stellen, in meinem Keller läuft ein (total oversized) Cluster. Mit den üblichen...
Thank you all for your hard work in mitigating the identified kernel exploits and backporting the fixes. We greatly appreciate your efforts!
With these security updates in mind, has the Proxmox team considered implementing live kernel patching...
We will re-evaluate it, but cannot make any promises.
What we also look into periodically is reducing the attack surface in general, like we started rolling out some simple but relatively effective approach to block autoloading of various niche...
The deprecation itself was not strongly influenced by that, but the decision to communicate it more actively was in fact primarily driven by it. Normally, we only mentioned it on the side once a new kernel became the default. In the past, we...
Out of curiosity, is this decision primarily driven by the recent wave of Kernel security vulnerability disclosures, or has there been a particular subsystem or area in the 6.14/6.17 series that has proven especially difficult to stabilize...
Hello,
Given the recent high churn of problematic issues, we decided to more actively announce the end of support for the 6.14-based kernel series.
We prolonged the life of that series significantly beyond what was originally planned.
At the...
The certificate expires on June 27, 2026. After that, Microsoft will no longer be able to sign shims with that certificate. Then it'll depend on how quickly Debian (and other distributions) will release new shims. However, you can simply enroll...