Search results

Hello Forum! I read the documentation and wonder if i need a new name for a node which i reinstalled. There are 3 Nodes atm: pve01, pve02 and pve03. When i now shutdown pve03 and remove the node via shell from the reaming other 2 systems and reinstall pve03, can i add the node aggain under...

Hi fabian, thanks for your reply! I see, that also was the outcome of the thread i opend up when 5.0 was released, the reason why it was fast in pve 4.0 was that both nodes could write on the same disk for a short period of time which was fixed in the qemu version pve 5.0 shipped. That was my...

Hello Fabian, including the with-local-disks option? unfortunately im still getting 12 seconds downtime. Kind regards

Dear Promox Team, may i ask if there were any updates on this? kind regards

So i guess the solution atm is the best we will get in term of downtime time? Thanks for your effort! Kind regards

Hallo Fabian, thank you! Is it possible to install the package on a production system? Or, should it be done? I dont have an testenvoriment atm and dont want it to crash when i upate via your repo next time. Kind regards

Dear wolfgang, any updates so far? Kind regards

Hello, did u managed to gather new information? Kind regards

Thank you for your answer and more for your work and investigation process. Great work! Kind regards

Thank you for your answer! Unfortunately the changes didnt seem to change anything. Kind Regards

Hello! i just tested with directly installed 5.0 iso and the problem seems to be the same. 2017-07-08 20:21:40 starting online/live migration on unix:/run/qemu-server/100.migrate 2017-07-08 20:21:40 migrate_set_speed: 8589934592 2017-07-08 20:21:40 migrate_set_downtime: 0.1 2017-07-08...

Thank for your reply! As you wanted i opend up a bug. I hope its usefull and can be fixed in the near future. Kind regards

Still testing but until now i got: fresh 4.4 cluster installed via iso from you guys: Jul 07 19:09:07 starting online/live migration on unix:/run/qemu-server/100.migrate Jul 07 19:09:07 migrate_set_speed: 8589934592 Jul 07 19:09:07 migrate_set_downtime: 0.1 Jul 07 19:09:07 set migration_caps...

Mhh but how it comes that it gets back online exact at the same time? Ill setup a new cluster and get back to this asap. I also try to install 5.0 directly and give that a try. Thats doesnt seem to impact an migration, perhaps just the replication? qm set 114 --migrate_speed 25 update VM...

I see, that sounds strange! I dont know anything about coding but mybe its somehow related? Yes indeed, that setup itself has not changed, not more vms, nothing within the network plus i am migrating it using the exact same way (with local disks). I just did the 4.4 to 5.0 upgrade like your...

Thanks for your answer! The network shoulndt be overloaded. I have roughly 2 mbit traffic in&out total for my entire small network with 4x1G uplink for the switch and 2x1G for each node (IGMP resolver is also within my network). While the transfer one nic for each node gets full load but...

Thanks for your answer, dont get me wrong, It sounds cooky AF, your know your code, but trust me when i say its not 72ms, I can reproduce it for every vm, every migration, i losse all connections, Teamspeak, FTP, SCP; SSH.. I tested with Sites like isitdownrightnow.com, no icmp request get...

the thing it its not 71 ms, that would be great! It takes the 12 seconds between the two commands, since the vm seems down on the other node until then! It took this time until the 5.0 upgrade, but since then the downtime time isnt acurate anymore. Kind regards

Dear Promox Team, first of all thanks for the great work, as always! Is it normal the live-migration performance is way slower then before? Im using local discs and "qm migrate 107 hostnamehere --online --with-local-disks" for example to migrate a vm. The copy itselfs is fullspeed (gbit) as...

To be exact it seems to be the time until the ssh command is executed, so ~12 seconds. Kind Regards