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 }

@olivierlambert Hi all. We've deployed one client on the last version of XCP and XOA and we need to backup on S3 remote (installed on Ceph and working with all of our backup solution : Veeam, cinder...) Backup failed with 502 error on clean-vm step : { "id": "1772809915090", "message": "clean-vm", "start": 1772809915090, "status": "failure", "end": 1772811181179, "result": { "name": "502", "$fault": "client", "$metadata": { "httpStatusCode": 502, "attempts": 3, "totalRetryDelay": 70 }, I only have this destination (my customer needs to use 50To), how can i correcting this pb (a ticket opened in vates)

@AtaxyaNetwork Hello! I am on an XOA trial with no airgapping.

@florent I have tested in our dev environment backing up a 30GB VM, which compressed into 22GB and was uploaded in 739 parts of 40MB each. I will test a larger VM next week but I think this was successful test is already conclusive. Thank You

@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.

@wralb it is in master, we are preparing a patch release for XOA on monday morning with this fix

@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

@DustyArmstrong said: @TeddyAstie yarp. My bad, the VM has it as 00:08.0 but on the host it's actually 00:06.0, I just didn't think about the specifics of your request! 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 1636 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 38 Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=2M] Region 4: I/O ports at d000 [size=256] Region 5: Memory at fca00000 (32-bit, non-prefetchable) [size=512K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [64] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [c0] MSI-X: Enable- Count=4 Masked- Vector table: BAR=5 offset=00042000 PBA: BAR=5 offset=00043000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270 v1] #19 Capabilities: [2a0 v1] Access Control Services ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 00000100, Page Request Allocation: 00000000 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv+, Max PASID Width: 10 PASIDCtl: Enable- Exec- Priv- Capabilities: [400 v1] #25 Capabilities: [410 v1] #26 Capabilities: [440 v1] #27 Kernel driver in use: pciback thanks. So basically, there is a more annoying issue, as the device doesn't even have a ROMBAR, in this case, the VBIOS is likely in the VFCT ACPI table of host (which the guest can't see); which needs to be injected as a "fake" rombar for the guest to behave properly. That doable on its own, but it's quite tricky to integrate (and you would e.g need to extract VBIOS from VFCT using external tools). I just discussed with Xen/AMD people, and there are known issues regarding PCI Passthrough of integrated AMD GPUs (not specific to Xen AFAIU). There are some projects regarding alternative approaches to bring AMD GPUs to VMs (virtio-gpu native context) which is the current focus.

@florent I can try running this command next time memory usage is high and will report my findings!

@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.

And to really round this out, the MTBF for any of these is in the millions of hours (1.2-3M), that's a use time of 136.968 - 342.46 years respectively. Basically, if a drive dies, just replace it no matter what, but in the end the reliability of these drives is meant to outlast all of us. Unless you actually need some specific function provided in some form-factor or model, don't bother.

@DustinB doesn't it use the exact same mechanism? I have to find out.