guys, it is solved, but thats something i will file again under technological harrassment. it was a DNS Problem. the dns-servers at my hosting provider woudnt resolve properly, only when I forced googles DNS servers onto it did it work. thanks for the push

Indeed, it's using our cloudinit ready templates hosted on xen-orchestra.com, so you need a XOA.

VSS agent will disappear, so yes, quiesce snapshots will disappear too. But fear not, we have plans to introduce a new feature, called "RAM backups".

Hi I had exatly the same problem when I upgrade one of my four server from xenserver 7.1 to xcp-ng 8.0, one backup failed with error: job already running and the other finish normaly later! I upgrade Xo from 5.51 to 5.54 and it's Ok for this problem BUT I have a new problem, the cold backup to NFS and the Continuous replication to a Xcp-ng 8 server are REALLY slow !! One exemple: Start time: Thursday, December 19th 2019, 7:20:00 am End time: Thursday, December 19th 2019, 7:58:54 am Duration: 39 minutes Snapshot Start time: Thursday, December 19th 2019, 7:20:00 am End time: Thursday, December 19th 2019, 7:20:05 am Duration: a few seconds SRs Local storage (a70a93c4-4951-9bec-54ab-d45bb5039b44) ✔ Start time: Thursday, December 19th 2019, 7:20:05 am End time: Thursday, December 19th 2019, 7:58:52 am Duration: 39 minutes transfer ✔ Start time: Thursday, December 19th 2019, 7:20:06 am End time: Thursday, December 19th 2019, 7:58:50 am Duration: 39 minutes Size: 1.34 GiB Speed: 605.55 KiB/s I try to upgrade debian OS, upgrade VM (4cpus 3Go ram) but same problem for the moment Thanks in advance Edit: I do a manual test by copy an iso of 2G locally on the virtual machine Xen orchestra, to the same connected NFS for backup, and the performance is normal, 10 seconds for 2Go, it seems to be a problem with Xen orchestra system backup?

It's supported in XOA since 5.40 and all more recent releases. Just tick the checkbox and that's it

@ruskofd said in Build from source question: Why not using a systemd unit instead of forever ? This is exactly what I did. Created a service file in etc/systemd/system that points back to the xo-server bin file.

I'm not sure, I have not used cloud-init in centos. I'd imagine it's similar, you need to find the cloud-init config file in your centos template install, and edit it to prefer the nocloud datasource

Ping @pdonias

Restoring the whole VM is OK, because XO doesn't "look" inside the disk.

I'm pretty fine that anyone build a WHMCS connector to XO API

Thank you. Yes, I have installed the xscontainer though it does nothing.

Next thing I tried was Exporting the affected VM, delete it and import it again. This fails because after deleting the VM both VDIs / VHDs are still there. Also I can not delete them. The error says: [image: 1576141485072-f6ff6ad4-8a59-4424-9bb5-ff498f87989f-image.png]

I'm not overly familiar with SAML, but our plugin is based on this: https://github.com/bergie/passport-saml Let us know if you find something relevant.

@Jarvar You install them in each VM. See here for more details.

So is there anyone who would be so kind to tell me whether it is worth it trying XOA instead of XOCE regarding workload balancing? Anyone who knows if there are differences?

I think this is normal behavior when you have the Load Balancer plugin loaded. If you don't intend to use it, then unload it.

Hi @akurzawa, this would be quite a big feature, please open an issue if you have something precise in mind (a list of possible actions, what could trigger a workflow, ideally some use cases that couldn't be done without it, etc.). Also, a lot can probably already be done with XO's Web Hooks, xo-cli and a third party workflow tool in between.

thank you, that did it. i got the container plugin installed, shows the containers in the VM fine in XO, testing migration of that VM now

Tested with Chrome now, on chrome it works. So it seems only a firefox problem. I switched off the extensions ( https everywhere, ublock origin and privacy badger ) but still crashes. Had htop running on my client while crashing, no unusual increase in RAM usage while going to crash. Rebooted XO VM, now it is ok again with firefox. so for me the issue is closed, if somebody is bored and wants to look into some logs for bug hunting i am glad to provide them. i also restarted the toolstack on one of the pool members ( not master ) and the "no such host" error is gone.