Restart the toolstack on each server.

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

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.

@DCT said in Cannot Delete a VM Template through CLI or XE:

xe template-param-clear uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30 param-name=is-a-template

Try this instead --

xe template-param-set is-a-template=false uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30

Then try to access the VM in XO and disable the Protect from accidental deletion option. Hopefully you will be able to delete it once that's done.

@julien-f Technically, it is possible with post processing as I mentioned above. Here's an example using jq and awk --

 xo-cli --list-objects type=VM-snapshot | jq '.[]."$snapshot_of"' | sort | uniq -c | awk -F " " '{print "{\"uuid\":" $2 ",\"count\":" $1"}"}'| jq ' select( .count > 1)'

Output looks like this --

{
  "uuid": "07604606-e937-5147-2dac-c1b4280df234",
  "count": 2
}
{
  "uuid": "0f11c701-c5e5-b09b-4c5f-00cf38153783",
  "count": 2
}
{
  "uuid": "83139da5-48d5-33f6-79f9-79ea91a7163c",
  "count": 2
}
{
  "uuid": "fb4703e4-bfd6-47b8-3fd1-f1f52f9ed234",
  "count": 2
}
{
  "uuid": "ff8b29e3-4445-5b22-e475-450270f2a7f3",
  "count": 2
}

Note: I am not proficient with these linux utilities so there may be better ways to accomplish this.

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.

@stormi Updated and rebooted. I'll report back if I encounter any issues.

Updated Dell R620 / XCP-ng 8.1. Rebooting all VMs now, but they appear to be coming up just fine.

Seems to work fine here.

On a separate issue, what's the plan to address the existing vulnerabilities (see below)? Will any of these be addressed prior to the move to 6.x?

81 vulnerabilities (12 low, 14 moderate, 49 high, 6 critical)

I believe that you need to import the OVA in XO. You can convert it to a template once that's done.

I would think the one with the .OVA extension.

Yes, I would use the last option you posted. I found this post, which is similar to your situation.

What options did you select on the prior screen?

@NeilGrevitt I would suggest rebuilding your install with the following commands --

cd /opt/xen-orchestra
rm -rf node_modules
yarn
yarn build

Then you can try starting the service with sudo systemctl start xo-server.service

@Andi79 Have you tried using xapi-explore-sr to examine how this VDI may be related to other disks?

@Gheppy It is working correctly for me as well (W11 & FF107).

This is part of the health check that is enabled for the backup. If you click on the "unused VHD" link, it will expand to show you the path of the VHD in question.

I just experienced this myself, and it appears that XO automatically removes the detected VHD.

@ronivay said in FYI - Applying 11/3/2022 and 11/4/2022 Commits in XO from Sources:

Something has definitely changed in the build procedure that eats more RAM than it used to.

Agreed. Maybe @julien-f can add some insight into what has changed and how to successfully build from sources.