@olivierlambert This error does not ring a bell to me.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning. Thanks for update and the patch.

@olivierlambert said in Migrating from Intel -> AMD: I don't know, but what I can tell is the fact I myself migration my own production from Intel to AMD without any issue, so I really wonder why your guest can't boot Well it's weird... because happens with all Ubuntu 16 hosts too. For this Debian in particular, even after upgrading to bullseye, still won't boot on any AMD host, only on Intel ones. Finally I just reinstalled from scratch on an AMD host and migrated the data.

@olivierlambert Okey... it can be deleted from there directly, I don't know why I didn't try that in the first place. Thanks

@julien-f said in Task list enhancement: We don't to do special cases for some operations in XO 5, we'll revisit this in XO 6 which will bring the notion of XO tasks in addition to XAPI tasks. But we'll probably display the elapsed and estimated duration of the task though Regarding previous tasks, why do you need to hide some of them? How do you use these previous tasks? Hello Julien, Well, it's not really that I use them. It's just that being so filled with information not useful most of the times, it's quite unusable (with all due respect for your great job). Example of what for? To see how much it lasted an already finished VM moving/copy operation. Displaying elapsed (and estimated, and I know this won't be always 100% accurante, but will be under normal circumstandes tho) would be great. After all, knowing the size of the object that it's being copied/moved, you can always extrapolate how much is remaining knowing how much it's lasting at any given moment. Thanks!

There's a bug report about it: https://github.com/vatesfr/xen-orchestra/issues/4610 pdonias created this issue in vatesfr/xen-orchestra open Duplicate VM templates #4610