@warriorcookie Well I am at the point on almost giving up on the P400 and just go with an M2000. I currently have an AMD Radeon Pro WX2100 laying around but no luck with this one Plex...

@andrew Sorry guys not sure i understand the issue enough to answer, @olivierlambert has a way better understanding of it, think it's better you to ask him 😉

@jcdick1 Could it be the same problem described here?

I don't think you can reset power state with XCP-ng Center 🤔

@olivierlambert

Thank you. I will do this - If I am successful - I will post it here 🙂

@spunky_surveyor Random question, if you put the old CPU back, does it suddenly work?

That's correct 🙂

Thanks for the feedback @Kajetan321 However, I have 0 idea on what it means and how it would work. Assistance will be welcome.

@shinuza got it, thanks. sad of course(

"ansible needs a stable unique id to identify hosts"
not realy, with manual host lists awx download new every time and remove old\chenged info.
same for netbox integration.

for most of task just enough tags like linux, db, etc.

8.2.1 will be around with various improvements in a matter of weeks. But I don't think that's your true problem/question here.

Regarding your issue, I don't see any obvious way without digging further on why the dom0 can't mount (I bet on a network init problem in the dom0)

@ppikna97 Np, I was also using template_file originally but as its now deprecated there have been no builds released for M1 based Mac (leading/forcing me down the templatefile function route).

It happens 🤷 No worries 🙂

@olivierlambert Thank you, I've changed the settings on b2 to "Keep all versions of the file (default)".

@danp Thanks!

@olivierlambert Thank you 🙂

@theaeon No, that's a normal case and it's handled properly. The issue would be if one of the IPs has 2 IPs in the same field separated by a white space like: "x.x.x.x y.y.y.y", or if the field is just empty or anything else that doesn't look like a proper IP address.

If you want to check the addresses more thoroughly, you can install xo-cli with npm i -g xo-cli, log into your XO with xo-cli --register <XO-Server URL> <username> <password> and then run xo-cli --list-objects --addresses type=VM \$pool=<pool ID>.

@danp
Forgot to reply in time 😛

I updated to the latest version of XO (from sources).
Now everything imports fine.

You can close this thread if you want.