Commenting for my future self and others as I just came across this issue too and it's not overly well documented and comments on the forums are often missing a a full story for how to debug and get this working...... When using Ubuntu 24.04, the usual apt method of installing XE Guest Utilities via the command; apt-install xe-guest-utilities Works, but doesn't. It successfully brings through the Memory information through to XO/XOA/XCP-ng Server, but not the IP Address, which is a tad strange. When checking the version of xe-guest-utilities that is contained within the APT Repository that comes configured out of the box with Ubuntu 24.04 using the following command; apt info xe-guest-utilities You can see the response is that it is running version "7.20.2-0" (as at the time of writing, which is before running an apt update command. Even when after running an update command; sudo apt update Then checking what packages are available to be updated using the following command; apt list --upgradable xe-guest-utilities wasn't available for an update past this point unfortunately. So to uninstall xe-guest-utilities installed via APT, simply run the following command; sudo apt remove xe-guest-utilities Then install via XO/XOA/XCP-ng Guest-Tools.iso Mount + Command Line by following these steps. Firstly, Select the guest-utilities.iso from the Disk within the XO/XOA/XCP-ng Platform for the VM. Then SSH into the box/console view and run the following commands; sudo /dev/cdrom /mnt sudo bash /mnt/Linux/install.sh sudo umount /dev/cdrom What you will notice when you run the second command is that gets installed here is "xe-guest-utilities_7.30.0.12_amd64.deb" - So is further ahead. Then you'll need to use the following commands to start the service on boot and also start the service. systemctl enable xe-linux-distribution.service systemctl start xe-linux-distribution.service And that now results in the IP Address of the virtual machine flowing through to XO/XOA/XCP-ng, which ever you are using.

@florent That would be great. Thanks again!

@samuelolavo Thanks for your answer It's very weird because by seeing the command outputs that you pasted, it looks like everything is behaving as it should be. Even the PCI ID (segment:bus:device:function) seems to stay correct (0000:03:00.0) I'll ask others internally.

@flakpyro thanks for the test we are preparing a branch with some performance improvement , hopefully this time we found the right cause

Hello, following up on this. Can anyone help decipher what the issue is? I'm stuck on this trial deployment until I can get the storage configured. Thanks!

@florent One last update. I reverted to Master branch (6699b) yesterday evening and the backup ran without issues overnight.

@TeddyAstie Thanks for the update. I do actually have a VBIOS for that GPU, but I wasn't entirely sure what to do with it - is there a process to inject it? I've found resources for Proxmox and others, but I really like XCP and equally I don't want to migrate my entire setup just for that. If it's really tricky then I'm not too worried about it, as I say the VM actually runs the cameras perfectly fine on CPU alone, it's negligible. Edit: Looks like this post might answer my question: https://github.com/xcp-ng/xcp/issues/786 "Even when specifying romfile and rombar properties on the xen-pci-passthrough device in QEMU, the ROM region is not mapped into guest memory." timemaster5 created this issue in xcp-ng/xcp open PCI ROM BAR not exposed to guest when using xen-pci-passthrough #786

502 is an answer coming from your S3, telling the server is having an issue. Adding @florent in the loop

I've had a lot of updates happening in the homelab. I've replaced the T620 with an R740, expanded my storage for both HDD and NVME pools. Also did a little min-maxing on the hardware to help separate traffic, decrease some latency and jitter for internet traffic and introducing IDS There are a lot of additions and modifications, but I guess the other big one is setting up a Dell Precision 5820 with XCP-NG as a studio and prototyping rig. Replaced Ansible with AWX, added some more VMs and migrated others but in all that I've updated the diagrams as well! Will say that XCP-NG offers up the flexibility and performance that I've needed so far. Would love to try out the XOSTOR storage at some point but will have to move around my entire setup haha. This reference diagram breaks down each VLAN [image: 1772850854389-networking-and-vlans-reference-diagram.drawio.png] The physical equipment reference diagram gives a breakdown of the server equipment and NAS at both locations, including the home rack. It also shows a basic breakdown of each server configuration. [image: 1772850854434-physical-equipment-reference-diagram.drawio.png] The physical topology reference diagram gives a simplistic overview of the major networking and server equipment. [image: 1772850854468-physical-topology-reference-diagram.drawio.png] The logical topology reference diagram gives a more in-depth view of the networking, servers, VMs, VLANs and endpoint devices. [image: 1772850854364-logical-topology-reference-diagram.drawio.png] The colo reference diagram contains my off-site location with a rented dedicated server [image: 1772850854295-colo-reference-diagram.drawio.png] The Authentication reference diagram gives a break down of how user access is sourced or what security route it takes. [image: 1772850854275-authentication-reference-diagram.drawio.png] The shared storage and access reference diagram gives a break down of how most hardware interacts with each other in regards to network routing for users, endpoints, and member servers. [image: 1772850854483-shared-storage-and-acess-reference-diagram.drawio.png]

I looked into the backup job and i forgot to enable a few settings when recreated the backup job. After renabling the below settings i reran the backup job. The vm in question did a full backup. All passed. [image: 1772848089214-screenshot_20260306_204613.png] { "data": { "type": "VM", "id": "fb72a8d7-a039-849f-b547-24fc56f056ba", "name_label": "Work PC" }, "id": "1772833993844", "message": "backup VM", "start": 1772833993844, "status": "success", "tasks": [ { "id": "1772833993868", "message": "clean-vm", "start": 1772833993868, "status": "success", "end": 1772833994233, "result": { "merge": false } }, { "id": "1772833994652", "message": "snapshot", "start": 1772833994652, "status": "success", "end": 1772833997235, "result": "16f5fe19-207a-4d89-017c-3f9405d22231" }, { "id": "1772834490355:0", "message": "health check", "start": 1772834490355, "status": "success", "infos": [ { "message": "This VM doesn't match the health check's tags for this schedule" } ], "end": 1772834490356 }, { "data": { "id": "a5e54e04-d7e4-48cb-bafc-b2f306d39679", "isFull": true, "type": "remote" }, "id": "1772833997235:0", "message": "export", "start": 1772833997235, "status": "success", "tasks": [ { "id": "1772834004185", "message": "transfer", "start": 1772834004185, "status": "success", "end": 1772834489032, "result": { "size": 119502012416 } }, { "id": "1772834490368", "message": "clean-vm", "start": 1772834490368, "status": "success", "end": 1772834490475, "result": { "merge": false } } ], "end": 1772834490476 } ], "infos": [ { "message": "will delete snapshot data" }, { "data": { "vdiRef": "OpaqueRef:31692cb3-7c43-de83-2cc8-f2e39a0105c8" }, "message": "Snapshot data has been deleted" } ], "end": 1772834490476 }

@hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence. Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR. If you have extended downtimes of your VM migrations, then something is not quite right with your setup.

I am in the same situation as @vhaelan. same as in same iGPU (alderlake) passed-through, same output for those latest commands, same OS (Fedora CoreOS on latest Xcp-Ng stable). Tried current avenues suggested in this thread with no progress. It seems vhaelan has settled with CoreOS under Proxmox (which works!). He also mentioned it works in Debian under XCP-ng, though I haven't tested that myself. I would appreciate additional suggestions for troubleshooting to take this further, in case anyone has any other ideas.

All vms still on host 1 after setting Migration cooldown time to 0 this morning. Maybe bug or just ui bug. When set to 0 save config when you load the page the "Fill information" for Migration Cooldown setting is unchecked but 0 is still applied. If set to 1. and reload the box is check as expected.

@simonp I'm not sure which one as I can see 2 config.tom file. 1st is under "/root/.config/xo-server/" config.toml.txt 2nd is under "/opt/xo/xo-server/" config.toml2.txt Both config.toml attached. Thank you. Best regards, Azren

No worries, it happens! Glad you found the problem

@Greg_E Thanks, I've got another thread up and it's potentially being addressed!

@firefly because the underlying hardware that the VM has registered has likely changed, maybe substantially. A sysprep has the Windows system go through and validate what it's hardware is, it removes hardware specific drivers namely, but it does other stuff too.