I’ve been asked to compare Ceph with Xostor – has anyone had any experience with either? Are there any comparison tables available?
And does Xostor support data locality?

@Pilow Il semblerai que j'avais une vm sur le meme réseau (eth0) que le réseau des hotes, se qui devais perturber sans doute le réseau. Du coup a chaque fois que je la redémarais sa faisait déconnecter, mais la je n'arrive plus a répéter le probleme, donc bon pour l'instant je dirai que c'est okay. En tout cas merci

@Danp Okay thanks you

@Pilow Non les hotre sont en 172.16.20. ect et le xoa en 172.16.10. ect et oui il peuvent bien se ping

Est que si imaginons mes hote sont sur eth0 et ma vm xoa sur eth1 sa joue ? ou pas

@Pilow Okay mais cela ne m'avance en rien vue que mes hôte on rejoint le master déjà.

@Pilow A oui ? Tu peux détailler sur la méthode ?

Et du coup pour en revenir a mon problème de déconnection lors d'une création d'une machine ou autre je ne comprend pas ...

Et oui il y a bien 3 srv dans le pool

@Pilow Oui Oui mais la j'avais mis sa pour montrer juste et voir si sa pouvais régler le probleme, mais oui c'est bien le srv 2 le master. Sauf que imaginons le srv2 tombe ba il faut que les autre node soit renseigner pour qu'il puisse prendre le master ?

@Danp Sorry for the late reply – I was in fits of laughter and completely forgot to ask my question. My question is: when I want to shut down a node with VMs on it, the HA will cause the following:

@Pilow Désoler de ma réponse tardive, j'étais absent, et oui si je disabled le srv ou le pool est connecter (srv master) :

Voici le réseau si il y a que la que on config :

I have three nodes; initially, the master was on node one, then I moved it to node two. I set up Xostor storage with one SSD (230 GB) per host, shared across them, containing:

Here are the HA settings for the pool:

The VMs are configured as follows:

@Pilow Voici :

I've got a major bug: whenever I launch or create anything (SR, VM, etc.) or reboot, it logs me out (about half the time), and I can no longer see the VM or anything else. Et quelque temps apres sa reviens :

@MajorP93 I followed your steps exactly:

• Shutdown the VM
• Disabled nested virtualization in Xen Orchestra
• Enabled it again using CLI with:
  xe vm-param-set uuid=<UUID> platform:exp-nested-hvm=true
• Started the VM again

However, Docker Desktop still shows:
"Virtualization support not detected"

At this point, it seems more like a limitation of nested virtualization with Xen/XCP-ng rather than a configuration issue.

@MajorP93 I’ve tested everything and restarted the system properly (nested virtualisation enabled, Xen Tools installed, Hyper-V features enabled, full restart), but Docker Desktop still isn’t working.

Systeminfo displays:
‘A hypervisor has been detected’

Hyper-V cannot therefore function fully within the virtual machine. It appears that nested virtualisation on XCP-ng (Xen) does not offer full support for Hyper-V, which prevents Docker Desktop from working.

I therefore believe this is a limitation of Xen/XCP-ng, and not a configuration issue.

I'm getting back to you. I've enabled ‘Nested virtualisation’, and I've also run the following command in PowerShell within the VM: "dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-All /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart" in a PowerShell session within the VM, but it still isn’t working. Is this normal? Is Docker not working on Windows under XCP-NG?

But thank you for your time all the same.

Well, yes, you had to register with an email address and then update.

I was trying to install Docker on Windows, but when I got to the point where I needed to enable virtualisation, I couldn’t do it. Does anyone know why? Here’s what happened: And I can't turn it on