Ping @thomas-dkmt

Also, we might have better roles in the future to be sure other people without the right role couldn't use it.

Hi,

@nathanael-h might take a look if we have the same problem and/or if it's "normal". Ideally, create a support ticket to get an investigation faster than via a community post.

@afk Have you found anything ?

Question for @stormi or @yann

@nathanael-h will

Hmm good question. I don't think it's possible but worth discussing it internally. Adding @pdonias or @MathieuRA in the loop.

It is started, we should have repos soon and a first basic version for the end of the month

Hi,

Yes. As all pure XO features are available from sources. XOA gives you QA/test/certification, stable versions with an updater, and some extra resources linked to you account (config save in the Cloud, XO Hub etc.)

Hi,

You could have open a support ticket for those questions, you have a better guarantee to have an answer in time, but here's mine, small and quick but still:

1. No performance gain to keep the snapshot. It's more the opposite. Leaving the snapshot means it will be only removed in the next job, meaning you'll have more to coalesce. However, it's very stable, CBT tends to have some quirks from time to time, so worth trying on few VMs first.
2. I don't think it's possible now. I can ask internally if it's something that's planned already or doable in the future.

edit: due to the size of the infrastructure, I would strongly suggest to create a ticket, because for potential feature requests, this can speed up things

Note: we are working on creating XO clients for both Go and Python, and they will (as soon as we can) rely on the REST API.

Meaning you won't have this problem anymore

Stay tuned, I hope to announce the new clients for next XO release (end of the month)

Warm migrate doesn't use migration. It's better than cold migration.

Are you sure you have used specifically that feature?

Hi,

You can use warm migration to solve this. Also, we provide pro support and services to help you to migrate, it's probably a lot of time saved with our expertise

Hi,

Sorry I can't, I'm far too busy to enter those details. Hopefully, @Danp or @bleader could assist when they can (but no promises)

I think it's related to the recent console changes in XO Lite. Let me put the team in the loop.

Have you checked https://xcp-ng.org/blog/2024/02/22/using-packer-with-xcp-ng/ ?

@pdonias is working on it, he'll come back to you ASAP

I suggest to start reading https://docs.xcp-ng.org/troubleshooting/ if you need to do trouble shooting.

Hi,

You could use XO Lite, which is another alternative

Hi,

Arm isn't like x86. A Raspberry Pi is VASTLY different than an Ampere machine. It's like expecting to have something working on both your smart watch and your desktop computer.

We'll move forward on Arm thanks to XCP-ng 9.0, but the main target will be server-grade hardware, not Raspi5. Maybe it will in the future, but it's not a priority and might require a LOT of work.