Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.
The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.
There was a recent change that resulted in the launched module being renamed. You need to redo your service so that it loads ./dist/cli.mjs instead of ./bin/xo-server
You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.
You need a space between the URL and the user name.
Updated Dell R620 / XCP-ng 8.1. Rebooting all VMs now, but they appear to be coming up just fine.
@hvilches said in XCP-ng Center 20.03.00 released:
is-a-template ( RW): true
Looks like this is the culprit...
@flipsidecreations There's a new Netdata plugin, which appears to only be available in XOA Premium edition. It doesn't appear that you will be able to enable the new Advanced Live Telemetry using the versions you are currently running.
@olivierlambert The "quick deploy" via web worked correctly this time 
@stormi Thanks. I expanded the disk and now the build completed. I'll report back if I come up with any meaningful results.
Se esta for a única VM que está apresentando problemas, eu me concentraria nos logs da VM em vez de presumir que esse é um problema com o hipervisor.
FWIW, você tem uma configuração complicada e o xcp-ng 8.0 não é mais compatível.
P.S. Acima é via Google Translate, então, desculpas por qualquer gafe
Looks like the functionality has been removed -- https://github.com/vatesfr/xen-orchestra/issues/5800
I have a couple of VM that have got stuck in a paused state, on different hosts.
How did you confirm that the VM is in the wrong power state? Could be VDI instead.
Have you checked the logs for more details?
Have you checked under Dashboard > Health to ensure there aren't any VDIs attached to the Control Domain?
P.S. I previously used the method shown here to clear up this issue with a VDI
Sounds like you haven't defined a default SR. You can configure this on the Home > Storage view.
@jsawyer77 Did you follow the documentation when building XO? If not, then what process did you use?
Also, check to see if libvhdi-utils is installed and which version.
Verified on XOA (latest channel) and XO from source (commit 9139c5e9d6b4306ba4078e6fa128a36f65417792).
Jul 12 09:49:44 xoa xo-server[34753]: 2021-07-12T13:49:44.807Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 383905792 instead of 5756023296
Jul 12 09:50:21 xoa xo-server[34753]: 2021-07-12T13:50:21.822Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 276914688 instead of 8795528192
Jul 12 09:50:22 xoa xo-server[34753]: 2021-07-12T13:50:22.171Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 224483328 instead of 4898078720
Jul 12 09:50:42 xoa xo-server[34753]: 2021-07-12T13:50:42.791Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 818112000 instead of 10603714560
Jul 12 09:51:31 xoa xo-server[34753]: 2021-07-12T13:51:31.452Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 155260416 instead of 4904371712
Jul 12 09:53:35 xoa xo-server[34753]: 2021-07-12T13:53:35.773Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 1965677568 instead of 64415232512
Jul 12 09:56:25 xoa xo-server[34753]: 2021-07-12T13:56:25.822Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 2743777792 instead of 16093311488
Jul 12 09:57:01 xoa xo-server[34753]: 2021-07-12T13:57:01.591Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 6112759296 instead of 62800031232
Jul 12 09:58:38 xoa xo-server[34753]: 2021-07-12T13:58:38.577Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 1309108736 instead of 85782038016
Jul 12 10:00:58 xoa xo-server[34753]: 2021-07-12T14:00:58.217Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 425869312 instead of 20179571200
Jul 12 10:03:09 xoa xo-server[34753]: 2021-07-12T14:03:09.747Z xo:backups:MixinBackupWriter WARN incorrect size in metadata: 6333517312 instead of 292895396352
Appears to have been introduced here, which includes code to fix the issue yet it continues to recur during each backup.
The backups appear to complete successfully, so I don't know if these warnings are benign or indicative of a larger issue.
Thoughts?
git clean -d -f should work to remove any untracked files.
@joearnon You can actually do that via the web interface. Go to Backup > Restore tab and then click the delete icon next to the desired VM. You will be able to delete individual backups or all of them from the next dialog.