Search results

  1. J

    PBS4 problems with MEGA as an S3 Endpoint

    Thanks. Will try later and reply back.
  2. J

    PBS4 problems with MEGA as an S3 Endpoint

    https://bugzilla.proxmox.com/show_bug.cgi?id=6700
  3. J

    PBS4 problems with MEGA as an S3 Endpoint

    The main problem is that if i try to prune or delete manualy a backup it gives errors and the old backups are not removed.
  4. J

    PBS4 problems with MEGA as an S3 Endpoint

    From what i can see, it creates a separate folder for each stored file.
  5. J

    PBS4 problems with MEGA as an S3 Endpoint

    Hi Chris. I do not have versioning or object locking enabled and already enabled the Skip If-None-Match header but still the same.
  6. J

    PBS4 problems with MEGA as an S3 Endpoint

    Hi. With MEGA as an S3 Endpoint, PBS has a strange behaviour. This is the content of my cache HD: This is the content saved in MEGA: For one single backup, there is more than one folder on MEGA, but just 1 on cache HD. If i try to prune or delete backups it give me errors or if i try to...
  7. J

    PBS 4 mega.nz as s3 endpoint - missing header: date

    Hi. Tested with the latest update from today and it seems to be working now, no more error message. Awesome !!
  8. J

    PBS 4 mega.nz as s3 endpoint - missing header: date

    Hi. Same problem here and anxious for testing this great feature. Thanks for the great job.
  9. J

    QEMU 9.2 available on pvetest and pve-no-subscription as of now

    Same problem here. Linux VM with more than 2x cpu use.
  10. J

    virtio-win-0.1.262-1 Released

    I had the same problem but you can update the drivers manualy, one by one, and it works fine.
  11. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    After 2 entire days no freezes...for me the problem seems solved. Will report back if there is something new. Many thanks to the Proxmox team.
  12. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    So far so good. It seems that the problem is gone. With a windows server 2022 vm and around 60 rdp users no freezes so far. With 6.5 kernel after 2 or 3 hours i had to disable NUMA. lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits...
  13. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    Thanks for the kernel. Last night i´ve installed it on one of my servers that had the freezes and will report back soon.
  14. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    I fweber. I have made some more tests and for me the current kernel does not solve the problem and the freezes continue.
  15. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    The result of lscpu: root@pve:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 88 On-line CPU(s) list: 0-87 Vendor ID...
  16. J

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    Hello fweber. I installed this kernel yesterday and, despite keeping KSM disabled because it has no benefits in my case, I have the NUMA balancer active and I notice that the server does not have such high peaks in usage. Until then there were peaks in the CPU graph up to 9 and since yesterday...
  17. J

    UUID lost after changing machine type

    I have a similar problem with an accounting software shared with RDP on a windows server 2022 vm. If i set the machine to 8.1 version, i loose the software license and cannot use it anymore even after setting it back to 8. Have to restore from backup to solve the issue. I always have updated to...
  18. J

    PVE sending email notifications on successful backup jobs

    Same problem here after latest updates. Will try to reboot to see if it get solved.