Recent content by ctrlspace

Just confirming that the latest pve-kernel package DOES include the fix and I have tested it. Fixed version is pve-kernel-5.4.44-2 and appears to be available in both the no-sub and enterprise repos. The only "broken" package version is pve-kernel-5.4.44-1. Anything prior didn't have the issue.

Devs informed me it will be patched in the next kernel release. Closing.

The methods of providing access to a VM through the webconsole rely on creating virtual graphics devices that serve as the primary display for the VM. When you set your PCIE GPU as the "primary GPU", this virtual device no longer seems to fill that role. I don't think you can have both. If the...

It's the primary GPU, I think that would make this "intended functionality" You could try installing some form of remote access service in the VM to gain entry post-boot, but you'll really have to fly blind until then. If it's linux/bsd you may be able to add a serial device and have the early...

Hey guys, One of my servers recently upgraded to 5.4.44* which appears to follow the convention many other distros have chosen, enforcing kernel lockdown mode when secureboot is enabled. Secureboot is critical to our security posture for protecting our servers against evil maid attacks and...

Understood, thanks for the reply. That does make the workflow for spawning these a bit easier.

It's possible the Debian system backing Proxmox hasn't let go of the lvs vgs. Can you run `lvs` and `vgs` to see if the volumes/disks still show up on the Debian side despite being removed? If so, you might want to use LVM commands to remove them.

I am attempting to install PVE6.x on a custom Debian Buster install, and wanted to avoid having to go through package downgrade hell. Currently I am at the point where I would add the Proxmox repos to Debian, but I cannot use the enterprise repos to do the package installation (no license...