Search results

Thank you very much!!

Hi! Thanks for the patch! I would be interested to know how to build a PBS Version. So think it's better to wait for the Update

Hy looks like we had the same idea, so last day's I wrote one of my first phython-scripts. Please don't take a closer look to my code *lol* * The script starts from cron how often you want. * A "qemu ping" checks if vm is responding or not. If not, the script tries to ping via network. Name...

Hy let me know if I can help kr Roland

Hello We check status of the last PRUNE via Api -> Tasks. Since Version 2.2-3 the check is brocken. Does anyone know some changes in API? This Request is working on Version 2.2-1 and lower. On V2.2-3 the result is empty...

Hello Maybe someone can help this too Problem was that Replication-Time on Windows RDS Hosts with installed Office 2019 took long time. About 5 to 90 minutes each job. After some investigation i noticed, that the Replication-Log hangs after „freeze guest filesystem“. Same time on vm, the...

Guten Morgen fireon! Danke für deine ausführliche Anleitung. Mit pve-zsync habe ich schon VM's zwischen Cluster migriert, das Retourkopieren der Daten jedoch noch nie. Alles ist gut beschrieben, danke! sg Roland

Hy Der Provider meinte die Anbindung sollte via Glas erfolgen, nur kann ich natürlich nicht garantieren, dass die Latency bei rund 5ms bleibt. Daher war meine Frage ob es Erfahrungswerte gibt. Aber vermutlich wird pve-zsync die bessere Variante sein. The Proxmox VE cluster stack requires a...

Hallo an alle! Darf ich mal nachfragen ob hier jemand ein Cluster über 2 Standorte betreibt? Genau geht es darum, dass ein 2. Standort hinzukommen soll auf welchen die wichtigen VM repliziert werden sollten um im Falle eines Ausfalles hochgefahren werden zu können. Zwischen den Standorten...

Hy we have same problem on multiple Nodes. Most of them are Supermicro with AMD EPYC 7352 CPU kr

Hy i will search for an affected testsystem and will try ist thanks

Hy We have the same problem and using AMD Cpu's with amd64-microcode installed.

Also successfully testet with PVE 7.2.3 and virtio 0.1.215

Hy Looks like the trick with q35 and v6.0 or 5.x does not work anymore with PVE 7.1.10 This is my current solution System: Windows Server 2019 German Machine: Default (i440fx) 6.1 Driver: VirtIO 0.1.217 Nic: virtIO Disk Driver Virtio (2k19) Disk SCSI Installed by loading the driver via...

Folgendes hat bei mir geholfen: https://forum.proxmox.com/threads/gui-not-showing-any-data-after-update-to-pve-7-2-3.109020/post-468508

thanks, solved the problem

Darf mich mal anhängen haben am Testcluster das selbe Problem nach dem Update von 7.1.12 auf 7.2.x Danke

hmm interessting. changing to q35 always solved the problem by us. i don't have access to the system, is it possible to send some pics from devicemanager and the nic? kr Roland

is it possible to delete the disk and import it again? before first boot change to q35 (we always did this) If not possible, try to uninstall "storage driver" and "chipset drivers" which depends on pve in i440fx kr

Hy did you migrate the Windows-System or fresh installation? Dit you change the boot ordner in Menu Options? kr