@bdenv-r are you trying XOSTOR on 8.2 or 8.3 ? had many problem of performance and tap-drive locking my VDIs on 8.2 xostor would like to know if 8.3 xostor still have issues

@MajorP93 I'm running with Node v24.11.0 now (on Debian 11 and 12). There have been some issues with older versions of 24, but to seems fine at this time.

@Marc.pezin said in A list of events which may be worth attending: Hello John, Thanks a lot for sharing this list of events, we’ll take a look and see which ones best fit our audience and objectives. Until now, we’ve mainly focused on events in France or nearby for logistical reasons. In fact, we’ll be at KubeCon + CloudNativeCon in Atlanta next week and it will be our first time in the US. Starting next year, as our sales and marketing teams continue to grow, we plan to expand our international presence and join more events abroad, so your suggestions come at a great time. Thanks again for the recommendations! @Marc.pezin A very good one to target (at minimum), is one of the conferences and trade shows where Bitdefender is attending. They have lots of experience at defending systems against black hats, with their services and products. Especially 0-Day vulnerabilities and malware. A product they develop is designed to defend against malware infections on virtualisation stacks like VMware vSphere, Citrix XenServer and others. If you can meet them during the event, it may give the foundations for a new partnership and/or collaboration!

@olivierlambert Thought so just wanted to check. Thank you.

@olivierlambert Fun fact -lah is short for lazy ass human AI is coming... [image: 1761837446934-feb6ff1a-7269-4c37-84b8-8ed1d64c3d68-image.png]

@flakpyro said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu said in VM start stuck on "Guest has not initialized the display (yet).": You must run secureboot-certs clear if you're updating from 1.2.0-2.4 or 1.2.0-3.1 and have previously run secureboot-certs install with the above versions installed. Should we run this before installing the update or after 1.2.0-3.2 has been installed? You should run that preferably after updating all hosts. @lukasz_s said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu thanks for advice i've upgraded varstored and varstored-tools: rpm -qa | grep varstored varstored-1.2.0-3.2 varstored-tools-1.2.0-3.2 than i've cleared varstore with secureboot-certs clear should taht folder contain more files ? ls /usr/share/varstored/ KEK.uth PK.auth db.auth what about dbx file ? That file is not shipped with varstored nor needed for now. We're validating the final 1.2.0-3.2 and preparing our guidance for the official update.

There's some nice progress on @psafont's work regarding improved revert. I'm confident we'll get there

@Biz365 Warm migrations from ESXi are ESXi license dependent on what you have/had with ESXi. Otherwise you can replicate the VM using the migration tool and then manually shutdown the VM on ESXi and then power it on XCP-ng.

You can manually install XOSTOR yes.

@lastcmaster Hi, it's a known issue that guest agent versions are not reported after migration or suspend. Other functionalities (poweroff/reboot, suspend, network change etc.) should continue to work normally.

[image: 1762024637434-rack-configuration.drawio.png] [image: 1762024637451-authentication.drawio.png] I've had a lot of changes to the homelab and always new projects, as well as started on the diagrams again. A couple of other reference diagrams aren't finished, but here are two that are done! Created a Physical Equipment Reference sheet that expands on the hardware used and how, as well as an Authentication Stack that gives a reference of service access and authentication.

Just a reminder for myself, or other people in need in the future thanks again for all people who helped me understanding this Had to reinstall my entire XCP system, and almost forget how to configure Ldap plugin to only allow my admin accout to login So here's my Ldap plugin conf, to allow only admin user (member of specific group) to login. my AD is a windows 2K19 server with active directory without ssl. URI : ldap://dc.domain.net:389 no certificate info base : dc=domain,dc=net Credential : Fill = tick DN = full DN of service user (CN=xen,OU=service_account,DC=domain,DC=net) password = password of this account it's a simple account with no specific right, can only read AD and login User Filter, where it can stuck (&(sAMAccountName={{name}})(memberOf=CN=SG-XCP_Admin,OU=service_account,DC=domain,DC=net)) in real my OU have spaces inside their name, it work anyway. SG-XCP_Admin is a security group having my admin users inside ID Attribute : sAMAccountName and that's all.

This is an old thread, but I ran into this myself recently. While there is a link to deleting the entire XO configuration, I think I fixed it with a less drastic solution. Remember: I'm just a random dude on the internet posting dangerous commands to try. It worked for me, but your mileage might vary. I run Xen Orchestra in a container (Xen Orchestra, commit e8733 at the time of writing). So I got a command line in the container with: docker exec -it xoa bash Then I ran redis-cli to get a redis command prompt. I typed KEYS * to get a list of keys. One key I saw was: 7) xo:server_host:172.30.0.214". That's the IP of the host I was trying to join (the master of a single-host pool). So I ran: del xo:server_host:172.30.0.214 Then I restarted my container with docker restart xoa. After that, I was able to successfully add the host to Xen Orchestra. Maybe this will help someone else. It got me working again.

@pierrebrunet Are you aware if there is an official guide on how to use this with AzureAD ?

@CodeMercenary I spoke too soon. Came in last night and it sounded like it was ready for take-off. So I restarted the container. This is so ridiculous... I think I did get 24-48 hours of quiet. So, a recheck interval of many minutes is probably fine. I think by default they start at like 5 seconds, which is needless.