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...
This seems to have popped up on my cluster in the most recent upgrade. I am on 9.1.9 and I have been on 9 for a while. This is on every node of the cluster.
Errors that appears in the VNC window:
/root/.ssh/config line 6: Bad key types...
This seems to have popped up on my cluster in the most recent upgrade. I am on 9.1.9 and I have been on 9 for a while. Errors:
/root/.ssh/config line 6: Bad key types '+ssh-dss'.
/root/.ssh/config: terminating, 1 bad configuration options...
I just ran into this as well. It was pretty cumbersome because I also couldn't boot into rescue mode so had to do it via debug console on the command line installed. Is there a ticket open about this? Should looked into.
Hello,
A couple of days ago, I updated a cluster of 4 hosts from 6.17.13-4 to the latest 7.0.2-6.
Hardware configuration:
2x hosts with Xeon Gold 6148
2x hosts with Xeon E5-2660 v3
All hosts use Samsung PM1735 NVMe drives on ZFS
Everything...
Ahh, that makes sense. edited the post with the updated intramfs command!
In regards to nova, it's a relatively new addition to the linux kernel. There were some articles on its inclusion into the 7.0 kernel as the successor to noveau.
I had...
like many other sites and pieces of public infrastructure, ours is getting hammered by AI scrapers/bots as well. we try our best to implement counter measures, but it's a constant game of whack-a-mole.
See for example:
https://forum.proxmox.com/threads/unable-to-remove-kernel.183685/post-853446
Or another:
https://forum.proxmox.com/threads/kernel-update-fail-6-14-to-7-0-no-space-left-on-device.183763/post-853952
See for example:
https://forum.proxmox.com/threads/unable-to-remove-kernel.183685/post-853446
Or another:
https://forum.proxmox.com/threads/kernel-update-fail-6-14-to-7-0-no-space-left-on-device.183763/post-853952