@Pilow @acebmxer Thanx for your replies. And sorry, i havent seen your first reply between my last posts with the link to your existing Thread. So, i think this is some kind of a bigger thing. Will handle with care, but i have to leave for today. Maybe i have time to test the snapshot and revert workarounds on the weekend. But these are all production VMs. Have to coordinate. I have 2 NFS-SRs in the Pool. Will try to migrate VMs from one to the other and see if this helps. Kind Regards and thx again Alex

@pkgw I tested it with a cluster size of 2 megabytes. I got similar results to those with the default size.

From what I understand, the OS-to-iDRAC pass-through is a direct USB link between the host and the BMC, designed for the hypervisor host itself to talk to the iDRAC, not something that would naturally bridge through Xen's networking layer into a VM. That might be why the PIF shows up in XCP-ng but the VM still can't reach 169.254.0.1; the bare metal case works because the OS sits directly on the hardware with no virtualisation layer in between. If you need the VM to have direct BMC access, USB passthrough might be worth exploring; XCP-ng does support passing USB devices through to VMs (https://docs.xcp-ng.org/compute#usb-passthrough), though I'm not certain the iDRAC virtual USB NIC would show up as a passthrough-able device. Might be worth a mention to @Team-Hypervisor-Kernel to find out; others here will know more than me.

From what I understand, when XCP-ng reverts to a snapshot it restores the full VM state from that point (metadata included, not just the disk contents) so the creation date field would get rolled back along with everything else; that might be why it now matches the snapshot timestamp rather than the original. I might be wrong about the internals though. It's a bit confusing if you were relying on that field to track VM history, and I don't think https://docs.xen-orchestra.com/xo5/manage_infrastructure#snapshot-management covers this explicitly. Might be worth a mention to @Team-Documentation-Knowledge-Management; it's the kind of thing that catches people off guard because nothing warns you upfront that metadata rolls back too. My $0.02.

Hello again, The updates have been made available and RPU with xostor should be safe to run https://xcp-ng.org/blog/2026/05/07/may-2026-updates-2-for-xcp-ng-8-3-lts/