@dthenot said:

@probain Hello,

It's likely linked to the List index out of range bug.
That bug was linked to the SR scan failing to introduce CBT_metatadata VDI in the XAPI database, could you try to launch a xe sr-scan uuid=<SR UUID> and try again to disable CBT?
If it does not work, could you share the /var/log/SMlog of around the time you are trying to disable CBT?

I've sent you a DM for sharing the logs.. Unfortunately I "solved" the issue by deleting all snapshots related to each VM. Including CBT ones. That did make it so I could toggle CBT on the VDIs again.

But I've collected the logs for you.

This also seems like a good time to raise my suggestion to have somewhere at vates where we could upload details in a similar way to how TrueNAS does it. Suggested here: https://feedback.vates.tech/posts/69/suggesting-to-add-a-debug-file-option

Now receiving UUID_INVALIDwhen trying to disable CBT on a VDI.
Perhaps a result of fixing the "List index out of range"-bug?

XO Source: 5811d
Node 24

vdi.set
{
  "id": "57e0db3e-3131-40df-a620-c1118047b9d4",
  "cbt": false
}
{
  "code": "UUID_INVALID",
  "params": [
    "VDI",
    "7b179964-dec6-4e24-a13b-8c5c56efcd95"
  ],
  "call": {
    "duration": 2,
    "method": "VDI.get_by_uuid",
    "params": [
      "* session id *",
      "7b179964-dec6-4e24-a13b-8c5c56efcd95"
    ]
  },
  "message": "UUID_INVALID(VDI, 7b179964-dec6-4e24-a13b-8c5c56efcd95)",
  "name": "XapiError",
  "stack": "XapiError: UUID_INVALID(VDI, 7b179964-dec6-4e24-a13b-8c5c56efcd95)
    at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:65:5)
    at processImmediate (node:internal/timers:472:9)"
}

@olivierlambert

I will check back tomorrow when I'm back at that lab-pool. Sorry for taking your time thus far. I will provide more and better info tomorrow

@olivierlambert said:

So is it a display issue from XO or a problem for the tools? (not sure to get it).

What's the output of xe CLI?

This is me (jr-m4) from another (private) account.

Update: Details below are incorrect information.

xe Output for another windows 2025 guest, where I'm seeing the same behaviour

[16:25 xcp ~]# xe vm-list uuid=3d3b8ba4-09c1-039d-8d58-ec797e7a05c3 params=networks
networks (MRO)    : 0/ip: 192.168.80.234; 0/ipv4/0: 192.168.80.234; 0/ipv6/0: fe80::4496:9d87:690d:ccc7

I just noticed that one VM I did a revert from snapshot on. Now that VM has that same date as its creation date. This is not really what I was expecting... Although I can somewhat se the logic/reason. It being that one could argue that it was "created" by that reverting to snapshot.. It is not indicative of when the VM itself acctually was created.

Is this intended behaviour and working as expected?

probain said:

Unfortunately, commit https://github.com/vatesfr/xen-orchestra/pull/9727 doesn't fix this issue of the VM-console reloading constantly. With loss of focus as a result. At least not on XO6..

pierre-briffaux opened this pull request in vatesfr/xen-orchestra

closed fix(vm/console): fix VNC reconnection causing focus loss #9727

@dinhngtu

Seems that the 9.1.146 version still reports 9.1.145-77 to XO. It is listed as the correct version in "Installed programs" within the guest (Windows server 2025).

@HeMaN

I too would love this.
They'll probably ask you to submit via the feedback website. But let me know when you've done that, and I'll vote on it as well.

@olivierlambert said in Rust-based guest-tools... How are things going?:

The thing is that it works very well and doesn't need fixes… I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months.

I have indeed seen the stability of it myself. But the lack of updates made me worry anyway. But I'm really looking forward to the promotion to 1.0 as well.

Thanks!

I'm just curious

Looking at the commit history for the Rust-based guest-tools, from the Xen-project. https://gitlab.com/xen-project/xen-guest-agent

Shows the last commit being done october 2024.. What is the status of this project? Is it dead, in hibernation, or should the xenserver-tools be used instead?

Thanks

Also..
Thank you for taking a look at it and solving it so quickly, @florent

It is a quite nice interaction when reporting bugs that they are looked at and triaged. Not saying everything needs to be a priority 1. But I do appreciate being close to the process. And if I can help make things better by reporting bugs, in a hopefully constructive way. Then I'll continue to contribute my way.

@florent said in Setting "Protect from accidental deletion" breaks with backups and healtchecks:

the fix is merged into master

I can confirm that the problem has now been solved. And will mark the raised github-issue as closed as well.

@Greg_E
or just uncheck the "protection"-flag. But that get tedious very quickly. And I only had to do it on 6 VMs.

@greg_e & @florent
I have gone back through the commits, and I believe it is 0a042d2f54a74ecc11a377809272337cb5c880d9 that introduces the bugg.
https://github.com/vatesfr/xen-orchestra/commit/0a042d2f54a74ecc11a377809272337cb5c880d9

My last known good and working commit is the one just prior to it, a831ac7b213eb6fc7f05fbd466407d5cf379cfe9.

Tried with the latest commit (as the time of writing). 91c5d98489b5981917ca0aabc28ac37acd448396. But this didn't fix it, unfortunately.

Filed a issue/bugg-report on github for this

https://github.com/vatesfr/xen-orchestra/issues/9472

@pilow
A lot of updates can, and do, happen in a month or two

cloudrootab created this issue in vatesfr/xen-orchestra

closed Backup job failed: forbidden operation: destroy is blocked: protected from accidental deletion #9472

0 fbeauchamp committed to vatesfr/xen-orchestra

fix(xapi): correctly block operations

blocked operation on vm creation does not seem to work

also importIncrementalVm was not unlocking it at the end

@Pilow

I didn't have this before yesterday, which is when I updated. And I update from source regularly. So the regression has happened since the last few (<1w) days.

I'll step backwards and see which commit introduced the bug.

@Greg_E

Manually unchecking makes the problem go away..
And I can also delete manually (after unchecking the HC-vms)

Having the flag "Protect from accidental deletion" has since yesterday left me with plenty of restored VMs. In the backup logs, it indicates that this happens during the healthcheck.

This has happened on 3 out of 6 VMs
Update: The other 3 VMs were opt-out from Healthchecks. So that is why this didn't affect them.

commit: dd5f0cdaa9993fae25469bd1cb1d01d4f2123f44

 transfer
Start: 2026-02-04 12:16
End: 2026-02-04 12:16
Duration: a few seconds
Size: 2.01 GiB
Speed: 81.14 MiB/s
 health check 
 transfer
Start: 2026-02-04 12:16
End: 2026-02-04 12:35
Duration: 19 minutes
 vmstart 
Start: 2026-02-04 12:35
End: 2026-02-04 12:35
Start: 2026-02-04 12:16
End: 2026-02-04 12:35
Error: forbidden operation: destroy is blocked: protected from accidental deletion
Start: 2026-02-04 12:15
End: 2026-02-04 12:35
Duration: 20 minutes
Error: forbidden operation: destroy is blocked: protected from accidental deletion
 Clean VM directory 
 cleanVm: incorrect backup size in metadata
 merge
Start: 2026-02-04 12:40
End: 2026-02-04 12:41
Duration: a minute
Start: 2026-02-04 12:40
End: 2026-02-04 12:41
 Snapshot 
Start: 2026-02-04 12:41
End: 2026-02-04 12:41

said in ️ XO 6: dedicated thread for all your feedback!:

Windows guests Console - Reloads every 5-10s.

When trying to use the console for both my Windows 11 and Server 2025. The console reloads every 5-10s. This makes it borderline unusable. Since it resets the viewport/window scroll placement as well. Also the console seems to loose focus when this happens as well. Leading to have to click the console-section to get it in focus, to receive I am not seeing this behaviour in XO5 at all.

.
.
.
.
Unfortunately this is still present in commit 0a0ae5dc7ea6608612d105f6338ffe72d8bd9ed1 as well..

Update: I recorded the behaviour, for better clarification:
https://www.youtube.com/watch?v=PXpBFgSl31U

@majorp93

I've updated and added a node.js-installation to the role. Targeting the LTS-24 version.
I hope you find it to your liking.

Windows guests Console - Reloads every 5-10s.

When trying to use the console for both my Windows 11 and Server 2025. The console reloads every 5-10s. This makes it borderline unusable. Since it resets the viewport/window scroll placement as well. Also the console seems to loose focus when this happens as well. Leading to have to click the console-section to get it in focus, to receive I am not seeing this behaviour in XO5 at all.

I do not see the same behaviour on Linux (Ubuntu 24.04) guests. But they are cli-only. No X/Wayland

Commit: b89c26459cfd301bb92adf0a98a0b2dbab57e487
node: 24.12.0
Management agent 9.1.100-59 on both VMs

Windows 11 has GPU passthrough & bios
Windows Server 2025 - no GPU passthrough , uses uefi