@julienXOvates Ok, great. Sounds good...thank you Julien!

Also, do you all have GPU passthrough yet? I'm really needing that function for a VDI setup i have. Thanks!

Maybe I missed this somewhere...but in XO6 > Quick Actions, is it planned to add a Migration option there? I think that is a needed high action item. I don't see Migrate anywhere in XO6 (yet). BTW, I'm going through all the XO 6.x updates posts. I've not yet finished reading through them, so apologies if it was mentioned in one that I haven't read yet

@poddingue maybe it was this yr? Heck...the days & months just run together on me anymore I'll check that out. Appreciate it!

@poddingue said:
Depends which one you mean

Thanks for the update! I meant the one where the VM was hanging because of incorrect boot order; but, good to know about the other issues. I'm moderately ok on Linux, but not so much so to where I fully understand the long boot time you go into (& divinni in the other thread)

I had an issue in XO-Lite myself last yr. That sounds a bit like I had; or, I believe the issue was BIOS vs UEFI. If I created the VM with BIOS, I could boot/set it up...but not able to with UEFI.

Thanks!

I made it through the whole year's updates on this thread. Took me a while

I never saw if the VM UEFI issue was resolved in a patch to XO? (I'm on "sources")

Also, I scrolled around my XO6 UI...saw several changes since my last logon. You all are making progress! Glad to see. Would like to see some of the Pool ("Cluster") configs make it to XO6 sooner than later if possible (i.e. Load Balancing, HA, etc). Also, would like a "cleaner" config interface for those things than what's shown in XO5. BTW...if I'm missing those configs in XO6, apologies, but I hadn't seen them yet.

Appreciate all your efforts thus far!

Oh, and for those who are not aware, Veeam now officially supports XCP-ng for backup. Looking forward to them also enabling Replication like they just did for Proxmox.

Thanks!

@Pilow - so...I powered down the VM and re-attempted the RPU. It seems snapshots is a deterrent for being able to perform a RPU, because I see VMs migrating now so the RPU can run.

For specificity - yes, my XCP Hosts are identical (CPU, RAM, etc); there were no affinities set (see screenshot)
, etc.

Thank you for the assist!

I think @olivierlambert or his tech writers need to update the RPU requirements area of the docs. Snapshots cannot be present or RPU will fail. Weird why that is

@Pilow Don't think so...this is just a "test" VM; don't think I even knew you could create affinity rules for XCP/XO. Let me check...

And, to confirm...here's the screenshot (that vol shown is iscsi storage connected to both Hosts)

@Pilow Sorry for the delay...had to go to a mtg real quick.

Thank you for the suggestion...I was indeed able to paste in the VM GUID and get the VM name. No ISOs etc attached. And, the disk is indeed on Shared Storage BUT....it does have snapshots. Is that the issue? I'd rather not remove them if possible. If they are the issue, can I power off the VM and resolve this issue you think?

Thanks.

@Pilow hi...yes; thank you for that. I see the Hosts seem to have updated, but not able to reboot due to some VM (doesn't share the friendly/display VM name)...it appears. See below:

{
"id": "0mi3j7qhj",
"properties": {
"poolId": "06f0d0d0-5745-9750-12b5-f5698a0dfba2",
"poolName": "XCP-Lab",
"progress": 0,
"name": "Rolling pool update",
"userId": "dd12cef8-919e-4ab7-97ae-75253331c84f"
},
"start": 1763407364311,
"status": "failure",
"updatedAt": 1763407364581,
"tasks": [
{
"id": "9vj4btqb1qk",
"properties": {
"name": "Listing missing patches",
"total": 2,
"progress": 100
},
"start": 1763407364314,
"status": "success",
"tasks": [
{
"id": "yglme9v6vz",
"properties": {
"name": "Listing missing patches for host 42f6368c-9dd9-4ea3-ac01-188a6476280d",
"hostId": "42f6368c-9dd9-4ea3-ac01-188a6476280d",
"hostName": "nkc-xcpng-2.nkcschools.org"
},
"start": 1763407364316,
"status": "success",
"end": 1763407364318
},
{
"id": "tou8ffgte7",
"properties": {
"name": "Listing missing patches for host 1f991575-e08d-4c3d-a651-07e4ccad6769",
"hostId": "1f991575-e08d-4c3d-a651-07e4ccad6769",
"hostName": "nkc-xcpng-1.nkcschools.org"
},
"start": 1763407364317,
"status": "success",
"end": 1763407364318
}
],
"end": 1763407364319
},
{
"id": "0i923wgi5wlg",
"properties": {
"name": "Updating and rebooting"
},
"start": 1763407364319,
"status": "failure",
"end": 1763407364578,
"result": {
"code": "CANNOT_EVACUATE_HOST",
"params": [
"VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb"
],
"call": {
"duration": 248,
"method": "host.assert_can_evacuate",
"params": [
" session id ",
"OpaqueRef:0619ffdc-782a-b854-c350-5ce1cc354547"
]
},
"message": "CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb)",
"name": "XapiError",
"stack": "XapiError: CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb)\n at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202511170838/packages/xen-api/_XapiError.mjs:16:12)\n at file:///opt/xo/xo-builds/xen-orchestra-202511170838/packages/xen-api/transports/json-rpc.mjs:38:21\n at runNextTicks (node:internal/process/task_queues:65:5)\n at processImmediate (node:internal/timers:453:9)\n at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
}
],
"end": 1763407364581,
"result": {
"code": "CANNOT_EVACUATE_HOST",
"params": [
"VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb"
],
"call": {
"duration": 248,
"method": "host.assert_can_evacuate",
"params": [
" session id ",
"OpaqueRef:0619ffdc-782a-b854-c350-5ce1cc354547"
]
},
"message": "CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb)",
"name": "XapiError",
"stack": "XapiError: CANNOT_EVACUATE_HOST(VM_LACKS_FEATURE,OpaqueRef:492194ea-9ad0-b759-ab20-8f72ffbb0cbb)\n at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202511170838/packages/xen-api/_XapiError.mjs:16:12)\n at file:///opt/xo/xo-builds/xen-orchestra-202511170838/packages/xen-api/transports/json-rpc.mjs:38:21\n at runNextTicks (node:internal/process/task_queues:65:5)\n at processImmediate (node:internal/timers:453:9)\n at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
}

I checked all my VMs and they are all on shared storage..so not sure why a VM is not able to live migrate?...

Thanks.

I have a Pool of 2 test XCP-Ng Hosts. I saw yesterday I need 69 patches via the Pool. I've done RPU before without issue. I attempted yesterday, and nothing happened. I have a 2nd XCP-Ng lab with 2 Hosts and that one updated fine using RPU, though I only have 1 VM (XO) in the Pool. In this RPU failed Pool, I have about 10 VMs.

I do meet the requirements listed in the doc:
https://docs.xcp-ng.org/management/updates/#rolling-pool-update-rpu
..i.e. all VMs are on shared storage. Anyway to see why this is failing? I re-attempted the RPU after about an hr, but both the initial and 2nd try show as 0 progress:

Thoughts?
Thanks!

@lsouai-vates Great! Thanks for addressing this

@ph7 Ah, ok

@ph7 where are you seeing secure boot in XO-Lite? I don't even have that option After creating a VM in XO-Lite, I see boot settings and Secure Boot is shown as Disabled

@olivierlambert Thank you for looking into it Olivier; and...not that you all have extra time on your hands... ...but if you could enable being able to configure Host networking in XO-Lite, I think that would be a semi-urgent feature to release as well. Thanks.

@Greg_E Ah, ok..yeah...guess I did
Yep, agree. Really needs more functions...like networking (and elsewhere) ha

@Greg_E Ah ok; yeah...to keep the posts 'clean' on here, I think that would be best...if you can find yours?

@olivierlambert - I just removed my UEFI-based VM and created BIOS-based one. It booted right up to the ISO. So it appears lack of functionality with UEFI booting to ISO. Not sure if that's a function of UEFI in general, or lack of feature set of XO-Lite. Well, may be both. Would be nice to have that boot order feature in XO-Lite, like in XO, which should take care of the issue with UEFI booting to ISO.

@olivierlambert Greg, in my other forums post, confirmed this lack of functionality as well.

@olivierlambert There is nowhere in XO-Lite to be able to change the boot order. That is the issue. Lack of functionality for that.