@ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback

So first, it's not an XO issue, which helps to diagnose it. Then, it might be a subtle XCP-ng bug indeed.

@dinhngtu I'll try this on the next VM that exhibits the behavior as to not interrupt the end users on the completed VMs.

Indeed, and it's clearly stated at https://docs.xen-orchestra.com/community

@Andrew Hey budd, thanks for the pointer. That ISO worked, thanks.

@sid It seems I have to get my hands dirty and take a deeper look into Terraform / OpenTofu. I am not shure how well the other folks at work partially will have fun working with commandline versus the easy to use XO web GUI. Tailoring down the CloudInit files used is not really the basic idea behind this. I was rather going the oposite way and install / configure the stuff we usually bake into our templates on the fly while generating the VM via CloudInit. Thanks a lot for all the responses !

@olivierlambert minor update... its now been 48+ hours and task is still in the same state, not timed out yet.

Since I'm not used to using git, I was running a few tests on my "test" host. I had made a change in my "one line commando" My memory is not in best shape so I forgot the change and ran it in my update. Now It's sorted out and ran a new update and voila

@dinhngtu Thanks. I did verify that it does not have the revoked version on any of the hosts. I've also verified that this is only occurring with Windows 2025. I can V2V Windows 2022 or any Linux distribution that we've tried, without secure boot issues. Also, a fresh installation of Windows 2025 doesn't have the issue. I've opened support ticket number 7747017 for this issue. Hopefully someone can get it figured out. Thanks. Allen B.

@cmanos No problem, glad I could helped. As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround

What GPU do you have? I thought I read something about NVidia's newer stuff having vGPU without the expensive licensing and hardware. But it's possible I'm just conflating that with the increase in concurrent NVENC encodes. On the bright side, you can always get a cheap GPU and just do passthrough with it. I do that for my Jellyfin server with a 2060, it's very easy to do in XCP-ng now and works super reliably.

Whelp had 2 of them get stuck, and one fail from the automated backup this time. The first one where it failed completely doesn't happen very often, so I'm less worried about it. Just including it in case it might be relevant. [image: 1761925465159-98feeae2-c301-4c92-bb33-bb4a029b0bc3-image.png]

@olivierlambert Ok, thanks. Yes I'm eagerly awaiting XCP-ng 9 for testing.

I created a GitHub issue to track this feature request: https://github.com/vatesfr/terraform-provider-xenorchestra/issues/378 gCyrille created this issue in vatesfr/terraform-provider-xenorchestra open CPU topology (sockets/cores) for new VMs deployed via Terraform #378

@andriy.sultanov said in "Block migraton" option on the VM´s Advanced tab: @panzersrmm @panzersrmm said in "Block migraton" option on the VM´s Advanced tab: Hi! Is there a VM parameter that saves this "Block migration" UI button? I wasn't able to identify which one it is with command: xe vm-param-list uuid=<VMuuid> Thank you! How do you mean? Is the XO option not persistent? XO sets these parameters: # xe vm-list uuid=$UUID params=blocked-operations blocked-operations (MRW) : pool_migrate: true; migrate_send: true Which you can set like this yourself: # xe vm-param-set uuid=$UUID blocked-operations:migrate_send=true # xe vm-param-set uuid=$UUID blocked-operations:pool_migrate=true @andriy.sultanov Thank you for your answer! That's what I was looking for. I was looking directly at the VM parameters, with xe vm-param-list uuid=$UUID and I was directly searching for "blocked_migration". Now I know what to look for. @olivierlambert Thank you for pinging the appropriate team for the answer.

@Danp Looking into it looks like VMs were doing full backups everytime when suppose to be delta backups... Let me know where else i can look to verify, but this is what i see when i look at the backups. [image: 1762268475129-screenshot-2025-11-04-095944.png] [image: 1762268480566-screenshot-2025-11-04-100005.png]

Yes, they are created either: on demand for users when we need in XO 6 Now, XO 6 is becoming the main driver for new endpoint as the UI is providing more and more features.

Hey, sorry guys. Didn't have time to advance on that. I promise will put something to test during november.

There's some nice progress on @psafont's work regarding improved revert. I'm confident we'll get there

Have you read the link I've sent? It explains exactly the reasons and answer your question You can imagine that if we have hundreds of 3rd party scripts, each doing their own way to install, it means we'll have to de facto support them all, despite it's unrelated to Xen Orchestra itself. Which means spending resources instead of working on Xen Orchestra directly (or fixing XO bugs). That's why it's preferable to open a ticket in the Github repo of the script creator, because that's exactly there you'll find the right answer, and also making sure the script creator could even fix their scripts if needed. If you need community support in here, you have to install it by following the official documentation: https://docs.xen-orchestra.com/installation#from-the-sources