Latest activity
-
SSunilkumar reacted to t.lamprecht's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with
Like.
Hmm, OK, seems like this BIOS signature checking is broken, if you got some time and nerves you might want contact HP w.r.t. this, they are the ones that can help best. We'll look out for any other reports or findings to ensure we did not miss... -
SSunilkumar reacted to Darkbotic's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with Like.
In my case I'm just a home labber so not a business using high end or enterprise equipment. I'm using a HP EliteDesk 800 G1 TWR computer. This PC doesn't have the 2023 CA keys. Only 2011. I have another computer, same model, that I had to upgrade...
-
SSunilkumar reacted to t.lamprecht's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with Like.
What's your mainboard model and BIOS version?
-
SSunilkumar reacted to Darkbotic's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with Like.
For now, I think I found the issue. The new shim is signed with both 2011 and 2023 keys and my pc only has the 2011 keys. For some reason my PC is rejecting the shim signed with both keys so I had to remove the 2023 signature. Maybe downgrading...
-
SSunilkumar reacted to Darkbotic's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with Like.
I'm sure this is what messed it up
-
SSunilkumar reacted to Darkbotic's post in the thread Secure Boot Violation / Invalid Signature Detected after upgrading to Proxmox 9.2 with Like.
Now it won't boot unless I disable Secure Boot. I think it's related to the 2023 CA Keys. Probably 9.2 is using the 2023 but my BIOS only has the 2011 keys.
-
Bran-Ko reacted to FloUhl's post in the thread [SOLVED] Remove or reset cluster configuration. with Like.
systemctl stop pve-cluster corosync pmxcfs -l rm /etc/corosync/* rm /etc/pve/corosync.conf killall pmxcfs systemctl start pve-cluster Was the way in Proxmox VE 6 https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node Here it is again -
Jjklocker reacted to Impact's post in the thread [SOLVED] Unable to connect to internet when creating LXC without unprivileged container option with Like.
Please use code blocks to preserve formatting and don't censor so much and needlessly. Using local for virtual disks is a bad idea too (IMHO). Try to start the CT like this to get more information lxc-start -n 101 -F -l DEBUG Also try to enable...
-
Ssmileyz replied to the thread New 9.2 install - can't find 7.0.2-6-pve , not all the time.What do your EFI partitions look like? If it works sporadically maybe you have duplicate IDs and/or one of EFI partitions didn't update correctly. Can you run: cat /etc/kernel/proxmox-boot-uuids lsblk -f |grep vfat
-
Mmfederanko reacted to janus57's post in the thread [Feature Request] Web UI: Custom names, tags, or notes for virtual disks (ZFS, QCOW2, etc.) with Like.
Hi, You should check the bugtracker[0] and create a new entry if it doesn’t already exist. [0] https://bugzilla.proxmox.com/ Best regards,
-
AAbby2017 replied to the thread Hardwarer oder Software RAID.Moin zusammen, dieser RAID Controller ist verbaut ModelSmart Array P440ar Controller Firmware Version7.00 Ich denke wir werden die Hardware Raid variante bevorzugen ... Danke für eure Infos und Vorschläge.
-
KKrakish reacted to aaron's post in the thread [SOLVED] Licensing for nested PVE on single host with Like.
As mentioned, there is no feature difference if you have a subscription applied or not. With a subscription you get access to the enterprise repositories, which provide the most stable packages, and depending on the level, a subscription can...
-
CChrisTG74 replied to the thread Problem with worker VM start initiated by Veeam on PVE.I've just got a reply from Veeam support: I 'm a bit astonished that 9.2.x is still not supported by Veeam. However, I updated the plugin (one needs to uninstall the current one before) and will try if that fixes the problem. I will let you know!
-
CChrisTG74 reacted to superwinni2's post in the thread Problem with worker VM start initiated by Veeam on PVE with Like.
Workaround with always running workers is running fine since. On my standalone PVE-Nodes I also have to leave them powered on. Tip: Set the "Start at boot" Option to enable. So you don't need to remember to start it up after updating or...
-
Mmfederanko replied to the thread [SOLVED] File Transfer from an external PC into ProxMox Node.There is also the option of virtiofs [0]. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_virtiofs
-
Ssuperwinni2 replied to the thread Problem with worker VM start initiated by Veeam on PVE.Workaround with always running workers is running fine since. On my standalone PVE-Nodes I also have to leave them powered on. Tip: Set the "Start at boot" Option to enable. So you don't need to remember to start it up after updating or...
-
shanreich replied to the thread SDN, IPAM & DHCP.Yes, that is to be expected, the IPAM tab in Datacenter is what you pick when you choose `pve` as the IPAM option, otherwise the external plugin is used. What's the exact sdn config? cat /etc/pve/sdn/zones.cfg cat /etc/pve/sdn/vnets.cfg cat... -
MMateo_123 replied to the thread shim-signed update - should new shim be copied to ESP automatically?.This system was originally installed as Debian and Proxmox VE was installed on top of it. That's why the ESP has /boot/efi/EFI/debian/ Also worth mentioning - all boot-related packages on this host are Proxmox
-
fschauer replied to the thread LXC Consoles clear when switching between guests on Proxmox VE.There is none yet, but there is a patch on the development mailing list to add a scrollback buffer: https://lore.proxmox.com/pve-devel/20260121112335.84473-1-f.schauer@proxmox.com/ -
RolandK replied to the thread building pve kernel fails with make[2]: *** [debian/rules:281: abicheck] Fehler 1.yes sure, but i did not yet change the kernel sources at all. i'm getting the same error on debian12 now with language set to en_US HASH : bus_register : 0x822ffa38 => 0x08b3d7ec HASH : _dev_alert...