@bvitnik @redakula @irtaza9
This is how I filtered out with TAGS
Added a TAG Visa to the Template I wanted to show

Then I selected the tag in Edit my settings | Custom filters | Templates | Default filter

@Andrew said in All drop-down options are empty:

release 5.103.1

How do You do this?
Is it possible to choose exactly this release when running the update, or do you check github every day?
Sorry for this question but I don't know the github finesses

I increased the dom0 RAM from default 1.75 to 2 GiB
Hopefully this will do.

In the replication job I keep Replication Retention=2
So at the time of reboot, 03:48 UTC, there was 2 saved CR-jobs that ran at 01:10 and 01:40

According to the time in red markings, The first alert ran at 05:00 CET (UTC + 1 hour)

And this is from dmesg:
[ 0.994105] rtc_cmos 00:02: setting system clock to 2025-02-24 03:48:56 UTC (1740368936)

I can not figure out

1. why did the host reboot?
2. why did one of the CR-jobs start ??
3. why was there ~15 hours without any graph?

I have UPS with NUT-shutdown on the host and on my trueNAS, with no indication of power failure.

@deadman2141
Well, I didn't reboot it.
It did it to itself

@olivierlambert
All backups and Continuous replication ran fine during these ~ 15hours that the graphics was gone.
Do You have any clue what logs I can check

@deadman2141
I also had some problem with stats running 749f0
I had no stats for ~ 15hours and then the host rebooted
All backups and Continuous replication ran fine during these ~ 15hours.

https://xcp-ng.org/forum/topic/10520/weird-performance-alert.-start-importing-vm-for-no-reason./2

XCP-ng, updated
XO CE, commit 749f0 (now 2 behind)

For some strange reason, I got performance alerts every minute starting at 05:00 this morning.

XO was trying to start/import a VM without any reason to.

The backup of this VM is started from a Sequence-job and this job was run from 03:04 to 03:05

The ed2b-job has health check enabled, but should only run on 1st and 15th

I also run a replication job during the day outside the backup schedule

The VM has autostart enabled, and maybe the host crashed and when it restarted it somehow thought it should auto start the replicated VM
Unfortunately I did destroy the VM but I did read that it was started 32min ago, and this was around 05:30.
Now when I checked the Host performance, there was nothing in the graph

[11:23 x2 ~]# uptime 11:26:44 up 6:37, 2 users, load average: 0,10, 0,09, 0,10

The host did restart for some reason
I ran dmesg and at line 618 I found that I should run fsck
[ 3.459057] FAT-fs (sda4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Maybe this isn't a backup problem, but I started investigating it as that

Save config
Copy/clone Your XO to SAN
start the new, stop the old
Load the config into the new one

Maybe this should be placed in a XO6 feedback thread? Didn't find any.
And maybe You already know about this.
Anyhow, My 2 feedback's look like this

In XO6, the disabled jobs that are included in Sequences are shown as disabled.

This is how it should look like

I am running these jobs and the disabled ones are included in a sequence job

When the Continuous Replication job is running, I get this

@raider600
I also had this issue some week ago
Unfortunately I don't remember what I did to fix it.
But I would try the --force option

I am running XO as root

sudo su -
cd ~/xen-orchestra/
git checkout .
git pull --ff-only
yarn
yarn build --force
yarn run turbo run build --filter @xen-orchestra/web
systemctl restart xo-server.service
cd

@kagbasi-ngc
There has been some discussions about the perf-alert plugin in the last months.
I think You might need an update of XOA

edit: oops to slow

@rtjdamen
I was in the same situation
I made a new schedule, BCK-Man with a tag BCK-Man.
When I needed a manual backup, I added the tag to that VM

@waveguide
I used the PCI passthrough for my zigbee USB Dongle and it has been working perfectly since I installed it 2½ month ago

Tested OK on
Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz

@DustinB
Yes

@DustinB
Backup / Restore / trashcan

@ph7
5:30 pm

@DustinB
~17:30

@DustinB
The schedule I am testing is hourly with a pause when the other jobs are running

In the setup the Long-term retention of backups like this:

And this is the result so far:

We are getting closer to the weekly now.
Cant wait