@olivierlambert Ideally XCP-ng (xapi) could add this to a queue, and wait for some time before cancelling the task because it took too long. This also needs some kind of feedback that can be given to the user / client, which I think currently is quite undercooked (how to report is waiting on other migrations to the same host when a client asks?). For the time I think XO being aware that it can retry the operation would be simpler, especially because it already has code to do it for other operations

@bleader Hi, After a restart of the entire host, port 6640 is now listed when I trigger ss. But, unfortunatly, tunnels are not working, every VM on this host loose connection to other in the same sdn network. Exemple with an ping between two hosts : 2025-10-09T12:22:54.781Z|00026|tunnel(handler1)|WARN|receive tunnel port not found (arp,tun_id=0x1f1,tun_src=192.0.0.1,tun_dst=192.0.0.3,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_tos=0,tun_ttl=64,tun_erspan_ver=0,gtpu_flags=0,gtpu_msgtype=0,tun_flags=key,in_port=33,vlan_tci=0x0000,dl_src=56:30:10:5c:4d:ad,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=192.168.10.10,arp_tpa=192.168.10.20,arp_op=1,arp_sha=56:30:10:5c:4d:ad,arp_tha=00:00:00:00:00:00) 2025-10-09T12:22:54.781Z|00027|ofproto_dpif_upcall(handler1)|INFO|Dropped 61 log messages in last 59 seconds (most recently, 1 seconds ago) due to excessive rate 2025-10-09T12:22:54.781Z|00028|ofproto_dpif_upcall(handler1)|INFO|received packet on unassociated datapath port 33 If I migrate the VM on the third host to another, network came back. This is very strange, because the network I've choose to test it is one of firt of all created, not last one, so it have worked before, and not now. I don't understand why and what to do...

Ah... so I missed the fix by one commit and two hours... I can confirm it resolve it. Thanks!

Excellent news! Thanks for the feedback

@Kptainflintt you are welcome We are always delighted when we can quickly unblock a user! Have a good day and don't hesitate to come back if you have other issues in the future.

@olivierlambert thank you for your response. Just tested with another laptop : no more issue... Well, we will inform our future users and wait for v6 !

Thanx ! I will check out with your team at the start of the new year for subscription, maybe we will discuss about it. @olivierlambert said in User self-service creation automation: I don't think it's possible to treat that "automatically" as it's a very specific use case. However, it should be possible to script that using our API. I don't think so. It's definetivly not an hypervisor must-have feature, but cloud yes. If you are a cloud provider and providing compute to customers, you will want to build "plans" for subscritpion and assign it automatically when user create his account and choose is plan. It is the same thing here, instead of not having bilings and several plans. Have a nice Christmas !