Recent content by rdfeij

  1. R

    [SOLVED] PVE 8.3.0 - vmbr0 Works at OS Level but "Unknown Type" in Web UI & No /run/network/ifstate Created

    Just to add some information, just encountered the same. Solved by removing the extra empty line. It seems to have started from last run update to version pve-manager/8.4.10. The file was never knowlingly changed since a few years. I do notice some files in /etc/network were changed during the...
  2. R

    "PME: Spurious native interrupt!" Kernel Meldungen

    ethtool still solves it with kernel 6.8.12-9 (with me) but sometimes i have to change to rx-usecs 1 in stead of 0 to get it fixed. Then it stays fixed (can change it to 0 and 1) till next reboot filtering on the messages still fills up the /var/log/kern.log rapidly filling valuable SSD space...
  3. R

    user config - ignore invalid group member 'user@domain.tld' (bug?)

    https://bugzilla.proxmox.com/show_bug.cgi?id=5610
  4. R

    user config - ignore invalid group member 'user@domain.tld' (bug?)

    I'm sorry, dug into the issue deeper since it was some time ago, users are still in the groups but do not exist as user anymore. So problem is still there. I will report a bug
  5. R

    user config - ignore invalid group member 'user@domain.tld' (bug?)

    There is a sync job active running every 2 hours, shouldn't that have done the same?
  6. R

    user config - ignore invalid group member 'user@domain.tld' (bug?)

    Fixed by enabling 'Remove vanished properties from synced users'. It was disabled. I expected that Entry: Remove vanished users and group entries would be enough. Is this stil a bug then or did i misinterpret these functions?
  7. R

    user config - ignore invalid group member 'user@domain.tld' (bug?)

    Within our proxmox cluster we have an Active directory sync only used for login of our users (no OU assignments to automate grouprights). One of our users has been remove from the OU allowing him to login to Proxmox so the sync removed his username. However the user is still in the usergroup he...
  8. R

    Windows 11 VM with tpm in glusterfs: swtpm_setup fails

    Hi Fiona, You are correct, if i map the TPM disk first by shell the VM starts normally. Shutting it down again (it unmaps automatically) and start it again fails it again. But only on this node it works on 4 other nodes.
  9. R

    Windows 11 VM with tpm in glusterfs: swtpm_setup fails

    This was during a fresh start. VM shutdown, moved to faulty node and started again. Right after start it failed, HA tried again (same error) and then HA migrated/moved it (offline) to a non-faulty node where it started normally. The requested output bothers me, i get errors while running the...
  10. R

    Windows 11 VM with tpm in glusterfs: swtpm_setup fails

    task started by HA resource agent /dev/rbd0 TPM2_EvictControl failed: 0x14c create_ek failed: 0x1 An error occurred. Authoring the TPM state failed. swtpm_setup: Starting vTPM manufacturing as root:root @ Thu 15 Feb 2024 04:09:38 PM CET swtpm_setup: TPM is listening on Unix socket. swtpm_setup...
  11. R

    Windows 11 VM with tpm in glusterfs: swtpm_setup fails

    Not working host: proxmox-ve: 8.1.0 (running kernel: 6.5.11-8-pve) pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-9 proxmox-kernel-6.5: 6.5.11-8 proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8 proxmox-kernel-6.5.11-7-pve-signed...
  12. R

    Windows 11 VM with tpm in glusterfs: swtpm_setup fails

    Same problem running TPM from Ceph after cloning(full) from template. moved TPM to nfs share and VM starts normally. Moved back to ceph, again failure. Moved VM to another host and now it is working with TPM on ceph.. could there be any underlying hardware issue?
  13. R

    3 node mesh Proxmox and Ceph

    @VictorSTS This issue has to be brought back to a misconfigurement within FRR, although we tested and checked many times after rebuilding the FRR config it is now working. Thank you for your help.
  14. R

    VM lost network after migrate to another node

    Is this VM on a VLAN that is not available on the switchport connected to the host where you are migrating to?