@JSylvia007 "Fatal error: exception Unix.Unix_error(Unix.EIO, \"read\", \"\")\n" mmmm SR is failing ? can you restore the last known good state of this VM (in parallel of the one in production) and try to backup this restored version ?

Ping @Team-XO-Backend

@TeddyAstie Attached is the output you requested xen-cpuid -p.txt

Go for https://feedback.vates.tech/ and create one and upvote then We'll put it in the backlog. More votes = higher prio!

@Kraken89 I will look into the transition from the previous system to the new one maybe that's the key

@acebmxer Yes, 22 or 24 should work correctly. Some early versions of 24 had issues, but not currently. I'm running 24 and it is working.

@dinhngtu You rock - thank you!

@florent Just gave this branch a shot, trying to run replication job after running a backup job no longer results in a full replication but just fails with: [image: 1774545162961-511a987a-15ac-47b0-85a9-f70be2387f96-image.jpeg]

@Danp Yes, they are all 'empty': xe vm-cd-list --multiple | grep -i false doesn't give any output.

And this is the result [image: 1774531386302-screenshot-2026-03-21-at-09-31-45-backup.png]

Regarding the restore thing, it's clearly sub optimal, can you submit an improvement feedback directly to https://feedback.vates.tech?

@olivierlambert I agree that pass-through should just work. I couldn't seem to get the GPU acceleration to work on a linux guest when I tried it on a Debian guest and I know if had the supported kernel running on the guest. I suspect this is due to the two different graphics devices on the guest VM (XCP-ng emulated and the physical passed-through GPU) and needing some sort of adjustments in X (Xlibre in my case) in order to tell it to use the GPU even though there's no display attached to it. I dropped that effort awhile back as I had bigger tasks at hand...But that's my suspicion. I need to tell X to offload processing to the GPU somehow, yet render the output to the emulated graphics adapter on the guest. I've never really used GPU's for graphics acceleration on Linux. I don't game, and almost all of my Linux experience is headless server stuff. So I'm in uncharted territory for me.

Are the users from the oidc provider unique and not already present as local users? I ran into this issue because my already existing local user was the same as the oidc provided user

@dinhngtu Yeah, I suspected that as well. So I inspected the SR and it showed connected to both hosts (at least in the XO UI - I didn't drop to the CLI to really confirm). By altering my workflow a bit and slowing down, I seem to have found the right "sweet spot" of delay and the issue hasn't resurfaced. Here's what I'm doing now, when I need to revert the snapshots of all three VMs: In the XO VM list, I select the three VMs and power them off at the same time. I then start with VM1 and eject the ISO, VM2 and eject the ISO, then VM3 and eject the ISO. By the time I circle back to VM1 for the next step, about 10-15 secs have elapsed. I then start with VM1 and revert the snapshot, and repeat the same on VM2 and VM3. By the time I circle back to VM1 for the next step, another 10-15 secs have elapsed. I re-attach the ISO to all three VMs in sequence. Another 10-15 secs elapse. I then start with VM1 and power all three VMs sequentially. The entire workflow takes about 30-45 secs, and I'm finding that by doing this, the issue hasn't resurfaced.

@nikade more beautiful than scary, it goes in an usual place where no one lives as you can see on satellite view it's an effusive éruption, not explosive, i was barely 100m when taking photos and you can also poke lava with a stick if you want (but need appropriate masks because of harming gazes like sulfur) not the first time it goes to the sea, the island expands slowly no casualties except from some fishes

@User-cxs You are probably experiencing this issue. Just a guess because you didn't actually ask a question.

@blueh2o Ooops, sorry - I read your message the wrong way around. You're right, that sounds really weird in your case....

@User-cxs si ici :[image: 1774010356739-c9d11a94-06d8-4a3c-b191-f95b2e2ef6f7-image.jpeg] tu DISABLE le serveur. tu nous confirme que c'est "comme" le probleme que tu constates ? un XOA tout vide en page d'accueil ? tu re ENABLE, et ça reviens ok ? tu n'as pas de probleme réseau / micro coupures / host distant au XOA (ipsec/openvpn?) ? la déco/reco que tu as me fait penser a un simple probleme réseau (si ça reviens tout seul et aucun autre impact...)