Thanks for your feedback, @florent will take a look.

In your XOA URL, just add /v6 at the end.

You can check the new network view in /v6 of your XO URL

I will let @florent answering this one

You need to swap the template in priority. This might drastically change the result

Have you read the doc first? https://docs.xcp-ng.org/xostor/

This gives a nice overview on how it works

@dinhngtu said in Windows VMGuest changing network cause the guest to crash:

This is a driver bug that we fixed in XCP-ng Windows tools v9.0.9030 but hasn't been integrated by Citrix yet. You can try it out if you're not running a production system.

Gosh, we are now officially faster than Citrix to detect and fix bugs even in the Windows PV driver

It's your call, but there's no guarantee it won't break for now, as the code is relatively young.

Ping @florent

No worries, always good to have feedback

I think the dev working on it had personal issues few days before the release, so at worst it will be there in a patch release or in 5.106. There's so much things in the pipe, it's possible sometimes they aren't shipped on D-day. But it will be there finally

Is anyone around to confirm or deny the issue please?

Adding @dinhngtu in the loop

This is because the VM is likely too busy to migrate memory pages fast enough vs what's newly written.

Ping @thomas-dkmt

Thanks, I will make sure to add this in the official XO doc

All the details are here: https://xcp-ng.org/blog/2025/03/14/the-future-of-xcp-ng-lts/

There's no more than this at the moment

Hi,

1. Yes, that's the point of XOSTOR. Creating a shared SR with local drives
2. Very likely, especially with NVMe drives, read speed will be like using a local NVMe, so great perf
3. Not dynamically but you can add more after, yes

Hi,

What browser? It works here with Chromium and FF