@olivierlambert OH nice! That will be awesome, I can't wait to try it.

@olivierlambert No sir, I haven't. I was trying to build a new VM that I would then convert into a template.

Oh man, what a rookie mistake!!!

Thanks for pointing that out Olivier, I'm all good now. Sorry to have bothered.

Good-day Folks,

I am trying to create a new VM but I am unable to. Both the Network and SR dropdowns are empty and because of this the Create button is not getting activated.

I have a single host and the strange thing is, all networks show a connected status. Additionally, the storage tab of the host also shows all connected.

If anyone has run into this before, please offer some assistance on how you fixed it.

My Environment:

• Git: Xen Orchestra, commit 658c2
• xo-server: v5.100.1
• xo-web: v5.101.1
• XCP-ng: v8.2.1

@Darkbeldin Aaah, thanks for the clarification. Now I know....learned something today.

By the way, I've been so busy at work that I forgot my host has an iLO which I'd previously configured. I used it to gain console access and successfully rest the root credentials. I'm in and I have successfully reconnected XO to the host using the root credentials.

@Darkbeldin Oh? Dumb question then - why provide the option to join the host to the domain, if it's not recommended to actually do so?

Thanks, by the way, for the guide you shared. I will go through it later tonight when I can gain physical access to the host.

Good-day Folks,

My Environment:

• Host Hardware: HP ProLiant DL360p Gen8
• Host Version: XCP-ng 8.2.1 (GPLv2)
• Xen Orchestra, commit ba8c5
• xo-server 5.96.0
• xo-web 5.97.2

I'm fairly new to XCP-ng and yesterday I spun up a host, successfully connected it to XCP-Center and created a VM - upon which I installed Xen Orchestra (compiled from source using this installation script from Ronivay).

In my excitement, I immediately started tinkering away. As mentioned earlier, I connected XCP-Center to the host using the root credentials. I then joined the host to my Active Directory domain, and added a group (with Pool Admin role).

This is when I started noticing some weirdness. When I attempted to add the host to XO using the root credentials, it failed. So I attempted to login to the console, from both XO and XCP-Center, and then from SSH. All three attempts failed with the message, "login incorrect". During the installation I created a non-root user, that too is not being accepted. What worked eventually was to use a service account I had created in Active Directory, and that allowed me to join the host to XO, however, not to log into the host (via console or SSH).

What's strange is, the same root credentials are what XCP-Center is using to communicate with the host, so why can't I use it to login? I'm still reading through the documentation and any forum posts I can find on this, however, any help is greatly appreciated. Thanks.

@olivierlambert Aaah, thanks Olivier. Still learning.

Great product by the way. Hoping I can get comfortable with it enough to make a recommendation to my company.

@Danp - thanks for pointing that out, I must have glossed over it. Now that I think about it, the patches were host patches so definitely not XO related. My apologies.

@stormi - I wanted to try the update via CLI, as per the documentation, however I've not been successful gaining access to the host. It's rather strange. Both the root and the non-root account I created won't let me in - whether via console or SSH, even though it's the same root credentials that I've used to connect XCP-Center to the host. Another strange thing - XO would not connect to the host using the root account, so I had to use a service account I'd created in Active Directory. Still scratching my head on that one, but I don't want to convolute this thread with this.

Anyway, while waiting I decided to reboot the host. From XO, it wouldn't let me; complains that there's no where to move the VM to and that I need to use the force flag. Since there's no way to do this from the XO ui (that I've found), I went into XCP-Center and rebooted it that way. When it came back, I tried the patches again and this time they installed without any problem. So for now, this problem is resolved.

Thanks to both of you for your responses. I'm gonna blow away my entire setup and redo it to see if I can replicate these anomalies.

Good-day Folks,

My Environment:

• Host Hardware: HP ProLiant DL360p Gen8
• Host Version: XCP-ng 8.2.1 (GPLv2)
• Xen Orchestra, commit ba8c5
• xo-server 5.96.0
• xo-web 5.97.2

I was recently introduced to XCP-NG and XO. After much reading and watching various YouTube videos, I decided to give it a try yesterday. So I spun up a host, successfully connected it to XCP-Center and created a VM running Debian 11. Then using this installation script from Ronivay, I successfully compiled XO from sources and successfully connected it to the host.

As expected, after a few minutes XO prompted me that there were some missing host patches, so I followed the appropriate buttons to install the patches. Unfortunately, I ran into the following error:

"global name 'commmand' is not defined"

I performed a quick search online and came across this forum posting where the same issue was discussed and the conclusion was that it had been resolved in a later commit. Given that I just built XO yesterday, I wanted to submit this inquiry, in case the issue had reared up again or if someone knew of a workaround.

I noticed in the error message that the word "command" has an extra "M" in it - perhaps a typo? Finally, here's the complete error log: 2022-06-28T00_48_16.728Z - XO.txt

Any assistance is very much appreciated, thank you.