We are not energy efficiency experts, while EasyVirt people are. I think they already have some stuff and it might be just a matter of plumbing.

This will be likely handled by EasyVirt I suppose. Thanks for posting your idea!

You cannot share the same LUN between different pools (butyou can share the same SAN with different LUNs)

1. Yes you can
2. All VMs booted after the join won't use the most recent CPU features that you don't have on your old CPUs.

The only trick is for previously existing VMs with recent CPU: you need to shutdown then start then again to be sure they aren't using those features (features are applied on boot). So it's doable, but both options are possible.

Thanks!

@anthoineb or someone from the @team-storage, you might want to take a look (IDK if it's a known problem internally)

@Pilow Thanks, it's promising but we'll wait for more runs on your side If it's that, at least it's not a biggie in the end!

Hi,

Adding a VIF is like plugging "live" a new network card in a physical system. It's still up to your operating system to handle it. XCP-ng doesn't know what's inside a VM, it's up to the VM OS to do what it has to do (like on a regular physical hardware system).

Question for @stormi

Let me ping @bastien-nollet or @mathieuRA

Congrats!

Hi!

@team-storage will correct me but on top of my head:

1. Live migration needs to continue to write locally while the VM runs while copying the blocks on destination. This takes some ressources and time, limiting the transfer speed
2. Migration in general is limited by the Dom0 expert speed via tapdisk, which is a bottleneck. In real life, this allowed us to have migrations without disrupting day-to-day operations (not taking all IOPS), which is good for stability but not on purpose
3. Copy with compression is faster because all blocks are compressed so you are sending more data for the same time (therefore, faster) at the cost of more CPU cycles. Which in general is worth it, as you've seen.

Hi,

Have you read the release blog post? It contains many information, including a link to this:

https://feedback.vates.tech/?tags=xo-6&view=most-wanted

Feel free to upvote stuff in there to help sorting the priorities

This is the PR: https://github.com/xapi-project/xen-api/pull/6786

It's ready/reviewed, we are waiting for upstream merge. We'll make sure to re-ask for a merge ASAP.

Stay tuned!

last-genius opened this pull request in xapi-project/xen-api

closed stream_vdi: Only process allocated clusters for VHD and QCOW on XVA export #6786

Let me ask internally

Adding @team-storage in the loop

Hi!

Thanks for the feedback. Can you be more specific? This might be helpful if others would have the same issue Thanks!

Let me add @team-os-platform-release

Hi,

Keep your XCP-ng up to date and you are protected. Cf https://docs.vates.tech/security/advisories/2025/vates-sa-2025-002

Adding @team-storage in the conversation