@Pilow Agreed however as our xcp-ng hosts are in the cloud with OVH Cloud we cannot use a physical appliance. We are currently setting up a dedicated OVH server for pfSense.

Create an appliance with all those VMs and configure the order and delay inside it.

@fred974 It used to be (and probably still is) that You have to be reasonably near correct time for NTP to accept any changes.

Hi! I'm not sure who to ping exactly for this question @pdonias or @Bastien-Nollet maybe?

@acebmxer Great. These are some YAML basics. You should read more about it . Following AI instructions without understanding is not going to take you far.

@bazzacad great, glad it worked for you

Adding @clemencebx for review/ideas on this;

@mguimond Not sure how old your XO is but this is the current Commit. Master, commit 5349f. Suggest try updating and try again. Maybe someone from Vates will have more information.

Ping @Team-Documentation-Knowledge-Management

I think it's planned for XO 6 adding @gregoire in the loop

@Pilow - so...I powered down the VM and re-attempted the RPU. It seems snapshots is a deterrent for being able to perform a RPU, because I see VMs migrating now so the RPU can run. For specificity - yes, my XCP Hosts are identical (CPU, RAM, etc); there were no affinities set (see screenshot) [image: 1763483116773-cf9b9ae2-5363-4b66-b367-1b0474e54538-image-resized.png] , etc. Thank you for the assist! I think @olivierlambert or his tech writers need to update the RPU requirements area of the docs. Snapshots cannot be present or RPU will fail. Weird why that is

xe pool-enable-tls-verification Was exactly what I needed, thanks! Worked after that.

@Andrew What a day... Have two hosts and needed a RAM upg so scheduled these with OVH, one for 4pm and the other for 8pm. Plan was to migrate the VMs off the host being upgraded to maintain uptime. Got an email from OVH stating that due to parts availability the upg will not proceed and then they downed both hosts at 8pm to upg at the same time and that caused havoc today.

@Danp My apologies for not being more specific. I’m encountering an issue with XOA deployment on a home lab environment. Environment Details: Installation source: USB Hardware: 16GB RAM, 1TB NVMe HDD Initial install: Completes successfully Dashboard: Displays expected status Steps Taken: Installed XCP-NG from USB — installation and setup completed without errors. Verified dashboard — all components appeared healthy. Deployed XOA to the existing HDD — process executed as expected. Observed Behavior: After deployment, XOA appears healthy overall, but the final item labeled “NEW” does not appear in the interface. Expected Behavior: The “NEW” item should be visible after deployment. Mark

@stevewest15 these errors are normal on XO from source, since you don't have licenses the configuration to use for ipmi sensors depends on the bios strings . Could you post the bios string of your hosts ? Dell configuration is used if system-manufacturer' contains the string dell

@McHenry said in pfSense Guest Tools: I have been using pfSense with xcp-ng for a while now without installing the guest tools. Due to some networking complications I have decided to install the guest tools to eliminate this as the cause. Q1) Are the guest tools required on pfSense and what do they do? Actually no, their main functionnality is to provide some data (memory usage, IPs) to XCP-ng to report them upward, AFAICT, it doesn't impact behavior in a significant way. It's actually not "PV drivers". Q2) Are these tools being maintained? This version of the guest agent is very limited and ancient (I don't exactly what it does, but not much IIRC). We're working on a new guest agent in Rust, which actually works pretty well on Linux, Windows (actually used in latest Windows drivers) and FreeBSD (NetBSD is also possible, but current code lacks some platform-specific bits). But we still need to sort-out some issues (some technical and some others non-technical) before making it broadly available / making it packaged.

@cmanos No problem, glad I could helped. As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround

@edsilber After exploring the UI, I confirmed that it's not possible to schedule a one-time cron job from the XO-5 interface. We're prioritizing the development of new features for XO-6, so we'll take your suggestions regarding scheduling into account for the new interface. I propose an alternative: using the REST API to run schedules by creating your own execution script (if you are on linux: https://www.veeble.com/kb/scheduling-one-time-jobs-in-linux-using-at-command/). The REST API link is: {your-xo-url}/rest/v0/docs/#/schedules Please feel free to contact me if you have any further questions.

@dinhngtu Hi For my i made on offline Install to solve my issue, installed failed when downloading the kernel from servers, so offline install worked fine for me.