@olivierlambert Sure, I absolutely get that XO CE comes with absolutely no warranty and XOA is the supported, enterprise grade product. If the budget was there and if I was to decide on that I would be happy to use it. It might still be a good idea to update your documentation at https://docs.xen-orchestra.com/installation#packages-and-prerequisites to at least align it with the Node JS version that you actually use and test against internally. (The linked part of documentation advises to use Node 24 while you are shipping Node 20 in XOA.) During testing it looked like running XO on Node 20 behaves quite differently compared to running it on Node 24 when it comes to RAM management. It looks like this got also confirmed by other users in this thread. XO CE users actually using and testing the versions that you ship might be of value for finding bugs. I think the documentation should generally advise to use the packages that you target during development in order to make the experience as good as possible for everyone. Just my two cents.

To elaborate: it was already in progress, but delayed due to 1. the fact that I underestimated the impact (I thought we'd overwrite the file only when we'd modify it, not every update the package) and 2. lots of other priorities keeping the team busy. But it's clearly the reminder, and the help in better diagnosing it, that allowed to have it re-prioritized and (partly, we've mostly bought time to fix it properly, by simply avoiding to touch the file at all at the moment) fixed so fast.

It's not a problem with XO backups

Hello All, This issue seem to completely go away on a older branch/tag if i build it from below for XO: xo-lite-v0.17.0 So the issue I would think is coming from the newer version of XO. Not sure best way to test this. So I am going back to an older commit. If anyone has any suggestion I can try helping as its an annoying issue.

@florent I'll send you a link in DM, hope it helps with something. If not, it wasn't too much of an effort, thanks for your time so far

Keep us posted, happy to hear from it!

@florent "the export is done by one of the host of the pool" How is this host selected ? Is it the master one, the one hosting the VM, or the less busy one in case of shared storage ?

@MathieuRA As announced, I have now installed branch xo6/update-site-dashboard and it seems to be working. It no longer loads endlessly and shows me that I haven't configured anything yet Thank you very much!

Ouch. @andyhhp in case that trace rings a bell.

@busthead said in Windows 11 (Win11_25H2_English_x64.iso) Fails to Install: It appears I missed the key press to start setup Dont you know your are not suppose to blink when doing working. You might miss something Glad you figured it out.

@Greg_E or just uncheck the "protection"-flag. But that get tedious very quickly. And I only had to do it on 6 VMs.

@Tristis-Oris There are many features missing since it's alpha now, but you can open bug tracker request on github if you want to keep track of progress for this particular feature.

Does it work as you wanted now? If yes, probably something we can put in our official doc! Ping @thomas-dkmt

@henri9813 Ahh alright, I understand now! Thanks for clarifying.

@LoTus111 Hello, I attempted to reproduce the issue without success. Could you please share the logs with us so we can conduct a deeper investigation? Feel free to send them to me via PM.

@florent said in Problems import vm Vmware to Xcp-ng from import Vmware and OVA: @olivluca skip ssl check in the import form I already did that. In fact it connects and I can get a list of VMs to import.

Resolved. Patched the rest of the hosts. Restarted all the toolstacks for good measure. I can move the master role now, and deploy new VMs.

@cbaguzman for information, I made some changes on vhd-cli so in the future we'll get a more explanatory error message when a command failed because we passed an incorrect argument: https://github.com/vatesfr/xen-orchestra/pull/9386 b-Nollet opened this pull request in vatesfr/xen-orchestra closed feat(vhd-cli): prevent using invalid options #9386