Search results

  1. A

    After upgrade to 7.0 all VMs are down

    In your examples there also isn´t a auto vmbr# in front of the OVS Bridge. Also, if you add a OVS Bridge via webinterface there isn´t that auto vmbr# either. # is a placeholder for a number, yes. I want to point out again, that this topic is about OVS Bridges and IntPorts. My config looks...
  2. A

    After upgrade to 7.0 all VMs are down

    Alright, I think the issue is a missing auto vmbr#. After adding this to the interfaces file the bridge comes up. But when I add another bridge through the webinterface it wants to delete my change on the previous bridge and remove that auto vmbr#. So the issue is clearly in your template.
  3. A

    After upgrade to 7.0 all VMs are down

    Can you please confirm or decline my issue. I was able to add the bridge and the ports manually but most likely after a reboot they are gone again.
  4. A

    After upgrade to 7.0 all VMs are down

    Ok, and you say you can´t reproduce it? When you add a new OVS Bridge to an upgraded Node and then add a OVS IntPort to it? vmbr# looks like this: The IntPort looks like this: All added via the webinterface.
  5. A

    After upgrade to 7.0 all VMs are down

    Before I do that one question: is it normal that Proxmox now uses the Open vSwitch package from the Debian repository? Because that is the only package i get offered and I can remember that Proxmox got an individual one. I searched the pve-no-subscription repo for it (openvswitch-switch)...
  6. A

    After upgrade to 7.0 all VMs are down

    There is not one single word mentioning vmbr# in all the logs i checked. I manually recreated the ovsbridge via the webinterface and still it doesn´t come up.
  7. A

    After upgrade to 7.0 all VMs are down

    Hello, my upgrade to 7.0 went not very well. The VMs didn´t start with the following error messages: Regards, Afox
  8. A

    Windows Server 2019 - bad performance (cleanmgr, virtio)

    Hello, is anyone else facing the issue that certain tasks, for example running the cleanmanager (cleanmgr) are taking very long under Windows Server 2019? Depending on the size of the cleanup it can take easily one hour and more. Virtio SCSI, qcow2, tested with Virtio 0.1.185 and 0.1.190 Also...
  9. A

    Limit simultaneous backup jobs

    PVE 6.3-6 One is a weekly job and another a daily with different compression. Backups should run when the load is low so the timeframe is not very huge.
  10. A

    Limit simultaneous backup jobs

    yes, i´m sure. there was a global lock when the first job was running and you couldn´t run a second backup job (manual or cron). It was stating a "wait" status until the running job was finished and then the second job started. The problem with the current behaviour is that when the second job...
  11. A

    Limit simultaneous backup jobs

    The second job is a different backup job but on the same node.
  12. A

    Limit simultaneous backup jobs

    Hello, thank you for the answer but that is not my problem. The problem is running 2 backup jobs at the same time what is possible recently and wasn´t possible before. For example one backup job is starting at 12 o'clock and another at 13 o'clock. If the first backup job hasn´t finished until...
  13. A

    Limit simultaneous backup jobs

    Hello, on my node it is possible to start multiple backup jobs at the same time. As this often results in conflicts I want to ask how I can limit the simultaneous backup jobs? Thanks in advance. Best regards, Afox
  14. A

    Lets Encrypt JWS verification error

    Hello, I did everything via the webinterface. Created an account and then added the domain. Only thing I did unusual was that I first added the same domain for API and SMTP separately. Then after I realized that something was wrong as there weren´t two entries I deleted the only displayed...
  15. A

    Lets Encrypt JWS verification error

    Hello, when I use the same FQDN for both API and SMTP after successfully ordering the API cert the SMTP request throws an error like so: No SMTP cert was created at this point. When I then run the same SMTP creation request again it creates a second cert with the same FQDN. I don´t know if...
  16. A

    ClamAV update error

    Switching to incremental was working for me, thanks :)
  17. A

    Lets Encrypt Port 80

    Hello, to feel more secure I have the following question about Port 80 that has to be open for LE cert creation and renewal: Is there a service constantly listening on that port or just at the very moment when creation or renewal takes place? I have the same question for the PVE LE...
  18. A

    ClamAV update error

    Hello, I upgraded to PMG 6.4 and when I try to update the virus detector it throws some errors: Best regards, Afox