@doogie06
register cli: xo-cli --register http://url login
then remove all tasks: xo-cli rest del tasks

Merged. Works as intented, thank you.

Problem with broken package on rhel8-9 looks resolved now. Done multiple tests.

@DustinB said in New Rust Xen guest tools:

systemctl enable xe

yep, found them.
full steps for RHEL:

wget https://gitlab.com/xen-project/xen-guest-agent/-/jobs/6041608360/artifacts/raw/RPMS/x86_64/xen-guest-agent-0.4.0-0.fc37.x86_64.rpm
rpm -i xen-guest-agent*
yum remove -y xe-guest-utilities-latest
systemctl enable xen-guest-agent.service --now

@chrisfonte new tools will remove the old one during install.

@ckargitest that was fixed few weeks ago. Do you use latest commit?

@julien-f @olivierlambert
2371109b6fea26c15df28caed132be2108a0d88e
Fixed now, thanks you.

fixed with https://github.com/vatesfr/xen-orchestra/commit/8a0604c274fb2b72d7ebc7f97803d5ae770028d3

0 pdonias committed to vatesfr/xen-orchestra

feat(netbox): support Netbox v4.2 (#8417)

Fixes #8280
Fixes #7645
See Zammad#34699
See https://xcp-ng.org/forum/topic/10236/netbox-version-4-2-1-not-supported
See https://github.com/netbox-community/netbox/releases/tag/v4.2.0

@olivierlambert During RPU - yes. i mean manual update in case of failure.

@florent https://pastebin.com/vhLXZ94F

i tried https://docs.xenserver.com/en-us/xenserver/8/dr/backup.html#back-up-single-host-installations but, "command not found".

At this time, the meta restore works perfectly. I got all my VMs back, but

• since I don't believe in success, I didn't shut down the unavailable slave host, where the VMs was still running.
• After restoring on a new master, all the VMs were also running.
• except for IP conflicts, in that case I had double VDI usage!
• The old server was shut down ASAP, but some VDIs were still corrupted anyway.

This wasn't a critical issue, but after EMERGENCY restoration, I expected that the host would be in emergency mode and the VMs would be halted.

And next problem. How to restore info about VMs?
2nd affected pool https://xcp-ng.org/forum/post/95369 lost master, all VMs now running on slave which i can't connect.
If setup new host and reconnect it to SR, i only can get a VDI, not VM itself.

My pool died so i decied to restore it from backup.

• fresh xen install, retore metadata, everything looks fine, but i can't join any new hosts into this pool.
  https://paste.vates.tech/?ca81f43fd2d10456#Ay6yKRNTS8LDDSHTkin7eLppP33eAMS5grLrevuqf5rL

• ok, 3 hosts fresh install, joined into pool, restore metadata - i got pool with 1 host and others 2 removed from XO.
  2nd host unavailable, as i see it got same IP as 1st.
  3rd host - nothing happens.
  https://paste.vates.tech/?112eb74c063a36d9#cgQi8jsG4htscEtEtAUS9vqRWnGQvD6REXd3XAzCxK2

• i add 2nd host with his "old" ip to XO. But can't connect and can't remove. Probably, IP change happens at this time.
  https://paste.vates.tech/?2c81fd68ed70cff2#7jXMPfj8wGePEC6KDTpTX9GVDmc2kuLG9Kd7ueb6MfSv
  https://paste.vates.tech/?07a7b2f07f699815#5w3qM7R7eVAauQ7rGGN3Wwx5DgQF2QejbJZcQh949Uqu

Only way i found to remove it - disable, change ip to not existed, tried to connect, remove works after error.

That looks like bloody mess. No host mapping, random results, pool is blocked from any new hosts in future.

@olivierlambert damn it at very bottom of page) i checked the doc first.

@florent wow, easter egg. thanks.

How about to create public api resource like swagger? or maybe bundled with XO.

@DustinB I advise you not to decide for others what they should do. I'm tired.

@DustinB yes, you can do it.

@DustinB the problem is that wrong drivers could be installed on wrong OS without warning. nothing else.

@DustinB meh. This VMs cost me nothing, i spend zero time since it can't stop working. Not a my decision, not my job, not my problem.