Resolved by rebuild, and doing VM backup and metadata to trunas dataset.... Start Backup earlier. Be better then me

I provided some feedback.

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.

@dalem That looks awesome ! Glad to see nix/nixos getting more and more adoption. It must have been a pain to build the pkgs, thanks a lot for working on this. I'll give it a try when I manage to free some time. Have you considered upstreaming the module/pkgs to nixpkgs or is this too much work ? I have not contributed there yet so I don't know if it would get merged as is.

Hi! Thanks for the feedback. Can you be more specific? This might be helpful if others would have the same issue Thanks!

Same behavior: Tools from the ubuntu repo 7.20 don't work on Ubuntu 24.04 (but they work on ubuntu 22.04. But manually installing the tools from the cdrom (version 7.30) work fine

Cool, thnx for the info!

Hi according to gh, it looks like there is traction on this feature: https://github.com/xcp-ng/xcp-ng-release/pull/53#discussion_r2642865515 So it might be merged soon... rzr opened this pull request in xcp-ng/xcp-ng-release closed s/c/e/profile.d/history.sh: Add timestamps to history #53

Adding @team-storage in the conversation

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

@snk33 Excellent news!

And my cloud config: #cloud-config hostname: {name}% Network config: network: version: 1 config: - type: physical name: enX0 subnets: - type: static address: 172.1.1.2 netmask: 255.255.255.0 gateway: 172.1.1.1

Actually Alma Linux does have a variant for v2 CPUs so they can run 10.0. Just look for x86_64 v2 on the downloads page.

@pierrebrunet thanks for quick insight/fix, got back to stable to deploy templates, it is working

still having initial issue, even on latest XOA or XO CE

Tracked it down to it thinking there was a pool version mismatch... then when I tried to transition to a new master it would fail with Xmlrpc_client.Connection_reset ... digging deeper it was complaining that it couldn't restore from the wrong version. Lots of head banging later... I setup a backup for the pool metadata and forced the backup immediately. TADA... I can now change the master with no issues at all.

Restarting tool stack on master host of remote pool cleared the stuck job and backup was able run failed vms. Support ticket still open fyi.

@itservices Thanks Marc

@exetico I have updated my script. Please use your previous install file (if you have it saved) to remove your previous version (remember to save your config before running uninstall), before you proceed to install the new version.