@MathieuRA I disabled Traefik and reverted to my old XO config (port 443, ssl encryption, http to https redirection), rebuild the docker container using your branch and tested: it is working fine on my end now Thank you very much! I did not expect this to get fixed so fast!

@Gheppy if you can have downtime snapshot/revert works

As an observation ; I'm going to draw attention to @majorp93's point about rebooting the servers after ALL nodes have been upgraded. Historically we would move all VMs off master, upgrade master, restart its toolstack, then reboot master, then move VMs from Node 1 to master so we could begin the upgrade on Node1. Normally works ok but last time around it caused all sorts of problems. Previously it had felt right to upgrade master in its entirety including the reboot before moving on to the next host and rinse, repeat - but this cost us a lot of time, corruptions and pain. TLDR: Perhaps add a footnote to the docs that when upgrading a pool the reboots should take place as a final step across the pool only after all nodes have been updated.

@olivierlambert thank for that. Just to be clear the vm was not runing but shut down if that makes a difference. @ph7 Both firewalls are Unifi Enterprise fortress gateways. - https://techspecs.ui.com/unifi/cloud-gateways/efg?subcategory=all-cloud-gateways Both sites are setup with Site Magic VPN. So should be full 1.1gbps if accurate. [image: 1767705099263-screenshot-2026-01-06-081123.png]

@Bastien-Nollet okay i'll do that tonight and will report back

I just learned something new, thats awesome

@Pilow Does disk show up after you do the snapshot? If it is able to do the snapshot there is a high chance it can boot up. So try booting up (and check for disk) and shut it down and do the snapshot at that time if the disk show up. It helps to boot up on the old v5 commit and check from that side too if you have both copy before the commit update. Yep I can confirm that snapshot doesn't always work. But using the older v5 that used to work before the update does get it showing up on the newer v5 commit if I go through whole snapshot, revert, etc. one of those case work.

Yes but why it works with some and not others. I suspect the firmware version in the NIC itself.

@fcgo if the storage is shared : the export is done by one of the host of the pool If the storage is not the export is done by the host with the storage . Same for the host receiving the data The command channel, as you said, is always the master to the xoa (and eventually xo-proxy) So for a replication : [source SR] => source host =https export call=> xoa / xo-proxy =https import call=> target host => [target SR] if the xoa is running on the host doing an export, it does not use the physical network the network use between the host and SR is dependent on the storage used

@snk33 Excellent news!

Great job, worked perfectly! Thank you very much for your fast support!

Thank you guys! Problem temporarily fixed by Vates support,

I also added windows build so that people can help with testing also on windows. It's a static build, no need for installer, just single zipped .exe file. No dependencies.

@TeddyAstie Sure thing: xl_dmesg.txt Dom0_dmesg.txt DomU_dmesg.txt

I have no clue, I usually back it up with XO, its the one called "XO config & pool metadata backup" and only had to restore it once.

@Pilow error reporting is a feature in itself . Thanks

Also works with alt driver (broadcom-bnxt-en-alt-1.10.3_231.0.162.0-1.xcpng8.2.x86_64) in 8.2.1: # yum install broadcom-bnxt-en-alt # reboot # modinfo bnxt_en filename: /lib/modules/4.19.0+1/override/bnxt_en.ko version: 1.10.3-231.0.162.0 description: Broadcom NetXtreme-C/E/S network driver license: GPL srcversion: 533BB7E5866E52F63B9ACCB alias: pci:v000014E4d0000D800sv*sd*bc*sc*i* ... alias: pci:v000014E4d00001604sv*sd*bc*sc*i* depends: devlink,ipv6 retpoline: Y name: bnxt_en vermagic: 4.19.0+1 SMP mod_unload modversions # dmesg|grep bnxt_en [ 15.047312] Broadcom NetXtreme-C/E/S driver bnxt_en v1.10.3-231.0.162.0 [ 15.048046] bnxt_en 0001:5c:00.0 (unnamed net_device) (uninitialized): Device requests max timeout of 60 seconds, may trigger hung task watchdog [ 15.215453] bnxt_en 0001:5c:00.0 eth0: Broadcom BCM57508 NetXtreme-E 10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem 2affff010000, node addr 40:5b:7f:6e:22:00 [ 15.215469] bnxt_en 0001:5c:00.0: 252.048 Gb/s available PCIe bandwidth (16 GT/s x16 link) [ 15.216606] bnxt_en 0001:5c:00.1 (unnamed net_device) (uninitialized): Device requests max timeout of 60 seconds, may trigger hung task watchdog [ 15.265361] bnxt_en 0001:5c:00.1 eth1: Broadcom BCM57508 NetXtreme-E 10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem 2affff000000, node addr 40:5b:7f:6e:22:01 [ 15.265372] bnxt_en 0001:5c:00.1: 252.048 Gb/s available PCIe bandwidth (16 GT/s x16 link) [ 15.350702] bnxt_en 0001:5c:00.1 side-5183-eth1: renamed from eth1 [ 15.385121] bnxt_en 0001:5c:00.0 side-3345-eth0: renamed from eth0 [ 17.400142] bnxt_en 0001:5c:00.0 eth0: renamed from side-3345-eth0 [ 17.493640] bnxt_en 0001:5c:00.1 eth1: renamed from side-5183-eth1 [ 20.614447] bnxt_en 0001:5c:00.1 eth1: NIC Link is Up, 100000 Mbps (NRZ) full duplex, Flow control: none [ 20.614454] bnxt_en 0001:5c:00.1 eth1: FEC autoneg off encoding: None [ 21.113687] bnxt_en 0001:5c:00.0 eth0: NIC Link is Up, 100000 Mbps (NRZ) full duplex, Flow control: ON - receive & transmit [ 21.113694] bnxt_en 0001:5c:00.0 eth0: FEC autoneg off encoding: None

@Danp To answer your earlier question about the state of the patched hosts, three hosts are currently fully patched with one of them as the current pool master. I've tried to promote both of the other two with the same "Cannot restore" error. For the sake of completeness I just tried promoting one of the non-patched hosts. Same error. And I'm still unable to deploy a new VM ("NOT_SUPPORTED_DURING_UPGRADE").