server has 10G DAC to dedicated 10G SW, Disk its writing to is a NAS iSCSI Target with a single 10GBe NIC. Network Traffic is low under 30Mb/s
png)
pdd.png
first peek is memory read.

@olivierlambert Re: SSH keys in XO
Great, thanks for your explanation!

There's a bug report about it: https://github.com/vatesfr/xen-orchestra/issues/4610

pdonias created this issue in vatesfr/xen-orchestra open Duplicate VM templates #4610

ok, could remove the vm by using the command

xe vm-reset-powerstate uuid=******* --force, then I could remove the host

See also: https://xcp-ng.org/forum/post/21792

See also https://xcp-ng.org/forum/post/21792

Yes, I would try that 🙂

@bcatubig 776ddfa2-a97c-4ea6-adb5-2dd05943b421-image.png

I see this message on the console right after the VM is created. Could it be somehow helpful?

For the moment I've had to create several backup jobs instead of one big backup it's e.g. servers01-06, 07-12, 13-18. Which isn't ideal as it's harder to manage, but is what it is!

So please open a support ticket, that would be easier to assist 🙂

Hard to say from just a screenshot.

What version of XO are you running? How long did you wait for the logs to load? Did you try refreshing the page?

FWIW, I've noticed that XO seems to take longer to load this page than it did previously.

P.S. Technically, you aren't running XOA (the pre-built XO appliance). 🙂

its still there ie the host is still atached to that vdi

im thinking this is the issue why my backups wont run anymore

if not i will do it on the xen server cli, but it would be nice to know why this isnt working

I've been spending some time on it for the last few nights, and my skills are improving little by little.

I think Ubuntu desktop was the closest I got to functional, there is a custom image for the Rpi3b+ that I found and it was one of the attempts that got to trying to start the XO-server service and failed. I was never able to get the xo-server to start manually either and the log files didn't give me anything I understood.

One of the versions that worked the least was CentOS 7 for RPi, node.js is not available for it in the normal repos. I have more experience with CentOS from a few years ago and more comfortable with it, may have to look into compiling all the dependencies from source to see if I can make it work.

I think an RPi 4b with 2gb or 4gb of RAM might be a better choice, but I have the 3b+.

Have you refresh your broswer tab? Have you tried to disconnect/reconnect the pool in Settings/servers?

Hey! Thanks for the feedback 🙂 Keep us posted if you have any issues!

@olivierlambert Thank you.
All back to normal now

You need a space between the URL and the user name.

This guide shows an old UI of XO, but you can always set the HA for the VM in its Advanced Tab.

HA at the pool level might be enabled using the command displayed in the blog post.

So far enabling HA on the pool level isn't exposed in XO because HA is causing more issues than it solves in general. If you decide to enable it on the CLI, it means that you probably understand what you do.

If you don't know where to find a SR UUID, using HA might expose you to VERY bad experience. BTW, you can find it in SR view, click on the SR you want to use as HA SR, you'll see the UUID just beneath the name.

As someone said in this forum few weeks ago:

Everybody wants HA but not everyone needs it

Also please note that's not a guarantee to boot the VM on this host. In fact, there's no way to be 100% sure it will. It's just than now XCP-ng will do its best to honor this. But eg, if there's not enough RAM on the host, then it will boot on another host of the pool.

I think, solution you are looking for is direct disk access. It's possible. I use it for my file server VM (FreeNAS) with five 4TB wd red drives (zfs). Passthrough entire PCI storage card is better, but even cheap server motherboards have 6 sata channels (one for dom0 ssd, and five for file server storage). 😉
This is my example (and my UUIDs)

mkdir /srv/direct-sata_sr
xe sr-create name-label=”Direct SATA SR” name-description=”SATA links to passthrough direct to VMs” type=udev content-type=disk device-config:location=/srv/direct-sata_sr

New UUID generated on sr creation
ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz

ln -s /dev/disk/by-id/<disk id> /srv/direct-sata_sr/<disk id>

ln -s /dev/disk/by-id/ata-WDC_WD5000BEVT-26A0RT0_WD-WXE1A10V7603 /srv/direct-sata_sr/ata-WDC_WD5000BEVT-26A0RT0_WD-WXE1A10V7603

xe sr-scan uuid=ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz
xe vdi-list sr-uuid=ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz

Good luck.