Recent content by Mecanik

  1. M

    Windows Server 2016 - Proxmox 7.3-3 - Impossible to install Virtio Drivers

    I found out the problem... if you install the OS with UEFI mode, no virtio drivers are accepted on 2016... for some unknown reason.
  2. M

    Windows Server 2016 - Proxmox 7.3-3 - Impossible to install Virtio Drivers

    Hi, As the title states, I tried installing virtio drivers from versions virtio-win-0.1.137 to virtio-win-0.1.185, each time on fresh install. They all report the same thing, "windows cannot verify digital signature"... Which leads me to believe that the virtio drivers were signed with a newer...
  3. M

    Listing backups via api for a specific vmid not working.

    Hayia.... I never thought of adding this permission because I trust and follow the documentation. Once again I was wrong to do so. Next time when I see someone adding links and insisting on docs I will get frustrated.... Thanks for the solution.
  4. M

    Listing backups via api for a specific vmid not working.

    I use the correct permissions as specified here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/storage/{storage}/content Pretty sure I know what I'm doing...
  5. M

    Listing backups via api for a specific vmid not working.

    Hi, why would I create another separate thread for the same issue? I won't even mention the fact that most of them are not replied to. Nevertheless, to answer your question: proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4) pve-kernel-5.15...
  6. M

    Listing backups via api for a specific vmid not working.

    I'm having the same issue, no errors in syslog however. Data returned is: { "data": [] } PVE 7.3-4.
  7. M

    IPTables rules per guest VM

    Because using a single VM with pfSense for many VM's is not ideal, it cannot handle that much PPS when under attack. If it was a separate dedicated server only for pfSense, sure.
  8. M

    [SOLVED] PVEFW Logs with custom rules

    Well, considering nobody gave a crap to even try and reply... I will leave my answer here. Looking at https://github.com/proxmox/pve-firewall/blob/master/src/pvefw-logger.c and following the log format will indeed put your custom logs into the VM firewall log.
  9. M

    IPTables rules per guest VM

    Just an update, I managed to do exactly what I needed. It is possible to add rules per guest and do whatever you need to do ;)
  10. M

    VM Notes "maximum length for this field is 8192"

    Update: It seems that you can manually add notes over the UI limit just fine into the vm.conf file. Not sure why the UI limits this.
  11. M

    [SOLVED] Question: Limits on VM Notes size?

    I have a new thread opened about this, it seems the character limit is 8192 at the moment via the UI.
  12. M

    VM Notes "maximum length for this field is 8192"

    Hello, I'm trying to leverage Notes to fit my needs, however I'm unable to save a small JSON snippet; I get the following message via UI: The maximum length for this field is 8192 Is there a workaround? Many thanks
  13. M

    [SOLVED] PVEFW Logs with custom rules

    Bump - nobody have any clue about this? :confused:
  14. M

    Proxmox 7.3-3 default SCSI Controller

    Ah I see... so no then. Each VM has only one disk. So this won't make a difference then.