I have similar problem. I have on root level / PVEAuditor role for group:
acl:1:/:@TestGroup-company.corp:PVEAuditor:
PVEVMAdmin role on /nodes to the same group:
acl:1:/nodes:@TestGroup-company.corp:PVEVMAdmin:
My expectation was that...
Seems it should be tpm-tis-device but proxmox generates "tpm-tis" as option for qemu?
root@pve-arm01:~# qemu-system-aarch64 -device help | grep -A2 -B2 tpm
name "tmp422", bus i2c-bus
name "tmp423", bus i2c-bus
name "tpm-tis-device", bus System...
Proxmox VE 7.1 - cryptojacking rootkit + root SSH backdoor: full teardown
TL;DR
Two PVE 7 hosts were compromised and running an XMRig cryptominer hidden by a preload rootkit. The same "install_and_mine.sh / libhide" toolchain planted:
A...
To be honest, I'm sick of this whole discussion. The newly registered users who were actually affected have already admitted that running an outdated system was a mistake. Meanwhile, some of the so-called veteran users on this forum just keep...
Yes, but during upgrade cycle you always have have some versions mixing. And sometimes it works, even if it is unsupported/untested. But not this case - and it is important to know how it behaves.
Well, they are older, like pve-manager/8.2.2 mostly. I can confirm issue is with versions mixing. Recycling name was not the issue. Upgraded one of older v8 to latest 9.2.10 and same problem. I started with upgrades, it should solve it.
Hi all,
I added a new node to my existing PVE cluster ( mixed versions — most nodes are 8.x, one is still 7.x, and the new node is 9.2.2).
Context: the node name "pve8" was previously used by a different physical node, which I properly removed...